Broadcast signal transmitting apparatus, broadcast signal receiving apparatus, method for transmitting broadcast signal, and method for receiving broadcast signal

ABSTRACT

An apparatus for receiving a broadcast signal, includes a receiver configured to receive the broadcast signal including physical layer signaling data, signaling data, content data and service guide information, wherein the signaling data is included in a signal frame indicated by the physical layer signaling data, wherein the signaling data includes mapping information between a service and a PLP, and information supporting channel scanning and service acquisition, wherein the service guide information includes a service fragment having information about the broadcast service and a content fragment having information about content data of the broadcast service, wherein the content fragment further includes a content-level PrivateExt element having component information of the content data, wherein the component information includes information for a component in the broadcast service, and wherein the component is one of a video component, an audio component, and a closed caption component (CC).

CROSS-REFERENCE TO RELATED APPLICATIONS

This Application is a Continuation of co-pending U.S. patent applicationSer. No. 15/115,567 filed on Jul. 29, 2016, which is the National Phaseof PCT International Application No. PCT/KR2015/004171 filed on Apr. 27,2015, which claims the benefit under 35 U.S.C. § 119(e) to U.S.Provisional Application Nos. 62/003,039 filed on May 27, 2014,62/000,515 filed on May 19, 2014, 61/991,624 filed on May 12, 2014 and61/984,854 filed on Apr. 27, 2014, all of which are hereby expresslyincorporated by reference into the present application.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to an apparatus for transmitting broadcastsignals, an apparatus for receiving broadcast signals, and methods fortransmitting and receiving broadcast signals.

Discussion of the Related Art

As analog broadcast signal transmission comes to an end, varioustechnologies for transmitting/receiving digital broadcast signals arebeing developed. A digital broadcast signal may include a larger amountof video/audio data than an analog broadcast signal and may furtherinclude various types of additional data in addition to the video/audiodata.

SUMMARY OF THE INVENTION

That is, a digital broadcast system can provide HD (high definition)images, multi-channel audio and various additional services. However,data transmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcasting.

The object of the present invention can be achieved by providing amethod of transmitting a broadcast signal, including generating serviceguide information including access information of a broadcast serviceand content data, wherein the service guide information includes aservice fragment indicating information about the broadcast service,encoding the generated service guide information and content data, andtransmitting the encoded service guide information and content data.

The service fragment may include service type information indicatingtype of the broadcast service, and the type of the broadcast serviceindicated by the service type information may include at least one of alinear service (Linear Service) that provides broadcast scheduleinformation, an application based service (Appbased Service), and acompanion screen service (CompanionScreen Service) using a companiondevice.

The service guide information may include a component fragmentindicating information about a component included in the broadcastservice, and the component fragment may include at least one ofinformation that identifies the component fragment, component typeinformation indicating type of the component, and component roleinformation indicating role of the component.

The type of the component indicated by the component type informationmay include at least one of a continuous component (Continuouscomponent) indicating a component represented in one continuous stream,an elementary component (Elementary component) indicating anindependently encoded component, a composite component (Compositecomponent) indicating a component that can be combined for onepresentation, and a pick-one component (PickOne component) indicating acomponent selected for one presentation.

The component role information may indicate that the component performsat least one role of a base layer for scalable video encoding, anenhancement layer for scalable video encoding, a left-eye image of 3Dvideo, a right-eye image of 3D video, depth information of 3D video,music audio, dialog audio, and caption for children.

In accordance with another aspect of the present invention, an apparatusfor receiving a broadcast signal includes a receiver configured toreceive service guide information including access information of abroadcast service and content data, wherein the service guideinformation includes a service fragment indicating information about thebroadcast service, and a decoder configured to decode the receivedservice guide information and content data.

The service fragment may include service type information indicatingtype of the broadcast service, and the type of the broadcast serviceindicated by the service type information may include at least one of alinear service (Linear Service) that provides broadcast scheduleinformation, an application based service (Appbased Service), and acompanion screen service (CompanionScreen Service) using a companiondevice.

The service guide information may include a component fragmentindicating information about a component included in the broadcastservice, and the component fragment may include at least one ofinformation that identifies the component fragment, component typeinformation indicating type of the component, and component roleinformation indicating role of the component.

The type of the component indicated by the component type informationmay include at least one of a continuous component (Continuouscomponent) indicating a component represented in one continuous stream,an elementary component (Elementary component) indicating anindependently encoded component, a composite component (Compositecomponent) indicating a component that can be combined for onepresentation, and a pick-one component (PickOne component) indicating acomponent selected for one presentation.

The component role information may indicate that the component performsat least one role of a base layer for scalable video encoding, anenhancement layer for scalable video encoding, a left-eye image of 3Dvideo, a right-eye image of 3D video, depth information of 3D video,music audio, dialog audio, and caption for children.

In accordance with another aspect of the present invention, an apparatusfor transmitting a broadcast signal includes a generator configured togenerate service guide information including access information of abroadcast service and content data, wherein the service guideinformation includes a service fragment indicating information about thebroadcast service, an encoder configured to encode the generated serviceguide information and content data, and a transmitter configured totransmit the encoded service guide information and content data.

The service fragment may include service type information indicatingtype of the broadcast service, and the type of the broadcast serviceindicated by the service type information may include at least one of alinear service (Linear Service) that provides broadcast scheduleinformation, an application based service (Appbased Service), and acompanion screen service (CompanionScreen Service) using a companiondevice.

In accordance with another aspect of the present invention, a method ofreceiving a broadcast signal includes receiving service guideinformation including access information of a broadcast service andcontent data, wherein the service guide information includes a servicefragment indicating information about the broadcast service, anddecoding the received service guide information and content data.

The service fragment may include service type information indicatingtype of the broadcast service, and the type of the broadcast serviceindicated by the service type information may include at least one of alinear service (Linear Service) that provides broadcast scheduleinformation, an application based service (Appbased Service), and acompanion screen service (CompanionScreen Service) using a companiondevice.

The service guide information may include a component fragmentindicating information about a component included in the broadcastservice, and the component fragment may include at least one ofinformation that identifies the component fragment, component typeinformation indicating type of the component, and component roleinformation indicating role of the component.

As is apparent from the above description, the embodiments of thepresent invention can process data according to service characteristicsto control QoS (Quality of Service) for each service or servicecomponent, thereby providing various broadcast services.

The embodiments of the present invention can achieve transmissionflexibility by transmitting various broadcast services through the sameradio frequency (RF) signal bandwidth.

The embodiments of the present invention can improve data transmissionefficiency and increase robustness of transmission/reception (Tx/Rx) ofbroadcast signals using a MIMO (Multiple Input Multiple Output) system.

The embodiments of the present invention can provide a method andapparatus, which are configured to receive digital broadcast signalswithout errors even with mobile reception equipment or in an indoorenvironment, for transmitting and receiving broadcast signals.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention.

FIG. 2 illustrates an input formatting block according to one embodimentof the present invention.

FIG. 3 illustrates an input formatting block according to anotherembodiment of the present invention.

FIG. 4 illustrates a BICM block according to an embodiment of thepresent invention.

FIG. 5 illustrates a BICM block according to another embodiment of thepresent invention.

FIG. 6 illustrates a frame building block according to one embodiment ofthe present invention.

FIG. 7 illustrates an OFDM generation block according to an embodimentof the present invention.

FIG. 8 illustrates a structure of an apparatus for receiving broadcastsignals for future broadcast services according to an embodiment of thepresent invention.

FIG. 9 illustrates a frame structure according to an embodiment of thepresent invention.

FIG. 10 illustrates a signaling hierarchy structure of the frameaccording to an embodiment of the present invention.

FIG. 11 illustrates preamble signaling data according to an embodimentof the present invention.

FIG. 12 illustrates PLS1 data according to an embodiment of the presentinvention.

FIG. 13 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 14 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 15 illustrates a logical structure of a frame according to anembodiment of the present invention.

FIG. 16 illustrates PLS mapping according to an embodiment of thepresent invention.

FIG. 17 illustrates EAC mapping according to an embodiment of thepresent invention.

FIG. 18 illustrates FIC mapping according to an embodiment of thepresent invention.

FIG. 19 illustrates an FEC structure according to an embodiment of thepresent invention.

FIG. 20 illustrates a time interleaving according to an embodiment ofthe present invention.

FIG. 21 illustrates the basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention.

FIG. 22 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention.

FIG. 23 illustrates a diagonal-wise reading pattern of a twistedrow-column block interleaver according to an embodiment of the presentinvention.

FIG. 24 illustrates interleaved XFECBLOCKs from each interleaving arrayaccording to an embodiment of the present invention.

FIG. 25 is a block diagram illustrating a main physical device and acompanion physical device according to an embodiment of the presentinvention.

FIG. 26 is a block diagram illustrating a protocol stack to support ahybrid broadcast service according to an embodiment of the presentinvention.

FIG. 27 is a conceptual diagram illustrating an XML schema of a ServiceType element according to an embodiment of the present invention.

FIG. 28 illustrates an XML schema regarding a specific service having aservice type value of 14, and an exemplary display image thereofaccording to an embodiment of the present invention.

FIG. 29 illustrates an XML schema regarding a specific service havingservice type values 14 and 15, and an exemplary display image thereofaccording to an embodiment of the present invention.

FIG. 30 illustrates an XML schema regarding a specific service havingservice type values 14 and 16, and an exemplary display image thereofaccording to an embodiment of the present invention.

FIG. 31 illustrates an XML schema of a Component Fragment according toan embodiment of the present invention.

FIG. 32 illustrates an XML schema of a ComponentType element accordingto an embodiment of the present invention.

FIG. 33 illustrates an XML schema of a ComponentData element accordingto an embodiment of the present invention.

FIG. 34 illustrates an XML schema of a VideoComponent element and aVideoRole element according to an embodiment of the present invention.

FIG. 35 illustrates an XML schema of an AudioComponent element and anAudioRole element according to an embodiment of the present invention.

FIG. 36 illustrates an XML schema of a CCComponent element and a CCRoleelement according to an embodiment of the present invention.

FIG. 37 illustrates an XML schema of component fragments regarding aComposite Video Component including one base layer and two enhancementlayers in scalable video coding according to an embodiment of thepresent invention.

FIG. 38 illustrates an XML schema of component fragments regarding aComposite Component including a 3D video left view and a 3D video rightview according to an embodiment of the present invention.

FIG. 39 illustrates an XML schema of component fragments configured todescribe a Complete Audio Component according to an embodiment of thepresent invention.

FIG. 40 illustrates an XML schema of a component element contained in acontent fragment according to an embodiment of the present invention.

FIG. 41 illustrates an XML schema of a content fragment regarding aLinear Service including Video, Audio, and CC Components according to anembodiment of the present invention.

FIG. 42 illustrates an XML schema of a component element when thecomponent element is defined in the content fragment so as to describethe association relationship among Video, Audio, and CC components.

FIG. 43 is a conceptual diagram illustrating an exemplary case in whichAssociatedTo attributes are used to describe the associationrelationship among Video, Audio, and CC components.

FIG. 44 is a conceptual diagram illustrating an exemplary case in whichassociatedAudio and associatedCC attributes are used to describe theassociation relationship among Video, Audio, and CC components.

FIG. 45 is a conceptual diagram illustrating the associationrelationship among Video, Audio, and CC components using AssociatedToattributes.

FIG. 46 is a conceptual diagram illustrating the associationrelationship among Video, Audio, and CC components using associatedAudioand/or associatedCC attributes.

FIG. 47 is a conceptual diagram illustrating the reference relationshipbetween fragments according to an embodiment of the present invention.

FIG. 48 illustrates an XML schema of a Component fragment including anelement indicating the reference relationship between fragmentsaccording to an embodiment of the present invention.

FIG. 49 illustrates an XML schema of a Schedule fragment including anelement indicating the reference relationship between fragmentsaccording to an embodiment of the present invention.

FIG. 50 illustrates the reference relationship among Service, Content,and Component fragments according to an embodiment of the presentinvention.

FIG. 51 illustrates the reference relationship among Component fragmentsconfigured to describe a Continuous Component according to an embodimentof the present invention.

FIG. 52 illustrates the reference relationship between Componentfragments configured to describe a component associated with AppBasedEnhancement according to an embodiment of the present invention.

FIG. 53 illustrates functions to be used when a content fragment refersto the associated service fragment according to an embodiment of thepresent invention.

FIG. 54 is a conceptual diagram illustrating an exemplary case in whichthe content fragment refers to the associated service fragment using therelationship attributes according to an embodiment of the presentinvention.

FIG. 55 is a conceptual diagram illustrating the reference relationshipbetween fragments according to another embodiment of the presentinvention.

FIG. 56 is a conceptual diagram illustrating a service fragmentincluding not only elements indicating the reference relationshipbetween fragments, but also a content fragment and an XML schema of thecomponent fragment according to another embodiment of the presentinvention.

FIG. 57 is a conceptual diagram illustrating the reference relationshipbetween Service, Content and Component fragments according to anotherembodiment of the present invention.

FIG. 58 is a conceptual diagram illustrating the reference relationshipbetween Component fragments describing a Continuous Component accordingto another embodiment of the present invention.

FIG. 59 is a conceptual diagram illustrating the reference relationshipbetween Component fragments describing a component associated withAppBased Enhancement according to another embodiment of the presentinvention.

FIGS. 60 and 61 illustrate the Component fragments according to anembodiment of the present invention.

FIG. 62 illustrates an XML schema of a Component fragment according toanother embodiment of the present invention.

FIG. 63 illustrates an XML schema of a ComponentType element accordingto another embodiment of the present invention.

FIG. 64 illustrates an XML schema of a ComponentRole element accordingto an embodiment of the present invention.

FIG. 65 illustrates an XML schema of component fragments regarding aComposite Video Component including one base layer and two enhancementlayers in scalable video coding according to another embodiment of thepresent invention.

FIG. 66 illustrates an XML schema of component fragments regarding aComposite Component including a 3D video left view and a 3D video rightview according to an embodiment of the present invention.

FIG. 67 illustrates an XML schema of component fragments configured todescribe a Complete Audio Component according to another embodiment ofthe present invention.

FIG. 68 is a structural view illustrating a Content fragment accordingto an embodiment of the present invention.

FIGS. 69, 70, 71, and 72 are structural views illustrating Componentelements according to an embodiment of the present invention.

FIG. 73 illustrates an XML schema of a Component element according to anembodiment of the present invention.

FIG. 74 illustrates an XML schema of a Language element and aComponentType element according to an embodiment of the presentinvention.

FIG. 75 illustrates an XML schema of a ComponentRole element accordingto an embodiment of the present invention.

FIG. 76 illustrates an XML schema of a DeviceCapability element and aTargetDevice element according to an embodiment of the presentinvention.

FIG. 77 illustrates an XML schema of a Component element when aPresentable Video Component (2D/HD) and a Presentable Audio Component(5.1 channels) are transmitted.

FIG. 78 illustrates an XML schema of a Component element when aPresentable Video component (UHD) and Presentable ENG audio componentare transmitted as broadcast signals and a Presentable SPA audiocomponent is transmitted as a broadband signal.

FIG. 79 illustrates an XML schema of a Component element when aPresentable Video Component (UHD/Wide Color Gamut) and a PresentableAudio Component (5.1 channels) are transmitted.

FIG. 80 illustrates a component element according to another embodimentof the present invention.

FIG. 81 illustrates a ComponentRole element according to an embodimentof the present invention.

FIG. 82 illustrates an XML-formatted component element according toanother embodiment of the present invention.

FIG. 83 is a conceptual diagram illustrating a Component elementaccording to another embodiment of the present invention.

FIG. 84 illustrates a PresentableCCComponent element and aPresentableAppComponent element according to another embodiment of thepresent invention.

FIG. 85 illustrates an XML-formatted component element according toanother embodiment of the present invention.

FIG. 86 illustrates Essential Capabilities elements according to anembodiment of the present invention.

FIG. 87 illustrates the meaning of Capability in response to aCapabilityCode element value according to an embodiment of the presentinvention.

FIG. 88 illustrates a Capability Category dependent upon a Categoryattribute information value.

FIG. 89 is a conceptual diagram illustrating a method for providing aPPV (Pay Per View) program to each component according to an embodimentof the present invention.

FIG. 90 is a flowchart illustrating a method for providing media to eachcomponent of a broadcast program according to an embodiment of thepresent invention.

FIG. 91 exemplarily illustrates screen images through which media issupplied to each component of a broadcast program according to anembodiment of the present invention.

FIG. 92 exemplarily illustrates screen images through which the role ofa video component is displayed on ESG according to an embodiment of thepresent invention.

FIG. 93 exemplarily illustrates screen images through which the role ofa video component is displayed on ESG according to another embodiment ofthe present invention.

FIG. 94 exemplarily illustrates screen images through which the role ofa video component is displayed on ESG according to another embodiment ofthe present invention.

FIG. 95 exemplarily illustrates screen images through which the role ofan audio component is displayed on ESG according to an embodiment of thepresent invention.

FIG. 96 exemplarily illustrates screen images through which the role ofan audio component is displayed on ESG according to another embodimentof the present invention.

FIG. 97 exemplarily illustrates screen images through which the role ofan audio component is displayed on ESG according to another embodimentof the present invention.

FIG. 98 illustrates an exemplary case in which the role of a ClosedCaption (CC) component is displayed on ESG according to an embodiment ofthe present invention.

FIG. 99 is a diagram illustrating a broadcast signal transmission methodaccording to an embodiment of the present invention.

FIG. 100 is a diagram illustrating a broadcast signal receptionapparatus according to an embodiment of the present invention.

FIG. 101 is a diagram illustrating a broadcast signal transmissionapparatus according to an embodiment of the present invention.

FIG. 102 is a diagram illustrating a broadcast signal reception methodaccording to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.

Although most terms of elements in this specification have been selectedfrom general ones widely used in the art taking into considerationfunctions thereof in this specification, the terms may be changeddepending on the intention or convention of those skilled in the art orthe introduction of new technology. Some terms have been arbitrarilyselected by the applicant and their meanings are explained in thefollowing description as needed. Thus, the terms used in thisspecification should be construed based on the overall content of thisspecification together with the actual meanings of the terms rather thantheir simple names or meanings.

The term “signaling” in the present invention may indicate that serviceinformation (SI) that is transmitted and received from a broadcastsystem, an Internet system, and/or a broadcast/Internet convergencesystem. The service information (SI) may include broadcast serviceinformation (e.g., ATSC-SI and/or DVB-SI) received from the existingbroadcast systems.

The term “broadcast signal” may conceptually include not only signalsand/or data received from a terrestrial broadcast, a cable broadcast, asatellite broadcast, and/or a mobile broadcast, but also signals and/ordata received from bidirectional broadcast systems such as an Internetbroadcast, a broadband broadcast, a communication broadcast, a databroadcast, and/or VOD (Video On Demand).

The term “PLP” may indicate a predetermined unit for transmitting datacontained in a physical layer. Therefore, the term “PLP” may also bereplaced with the terms ‘data unit’ or ‘data pipe’ as necessary.

A hybrid broadcast service configured to interwork with the broadcastnetwork and/or the Internet network may be used as a representativeapplication to be used in a digital television (DTV) service. The hybridbroadcast service transmits, in real time, enhancement data related tobroadcast A/V (Audio/Video) contents transmitted through the terrestrialbroadcast network over the Internet, or transmits, in real time, someparts of the broadcast A/V contents over the Internet, such that userscan experience a variety of contents.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, aUHDTV service, etc. The present invention may process broadcast signalsfor the future broadcast services through non-MIMO (Multiple InputMultiple Output) or MIMO according to one embodiment. A non-MIMO schemeaccording to an embodiment of the present invention may include a MISO(Multiple Input Single Output) scheme, a SISO (Single Input SingleOutput) scheme, etc.

While MISO or MIMO uses two antennas in the following for convenience ofdescription, the present invention is applicable to systems using two ormore antennas. The present invention may defines three physical layer(PL) profiles—base, handheld and advanced profiles—each optimized tominimize receiver complexity while attaining the performance requiredfor a particular use case. The physical layer (PHY) profiles are subsetsof all configurations that a corresponding receiver should implement.

The three PHY profiles share most of the functional blocks but differslightly in specific blocks and/or parameters. Additional PHY profilescan be defined in the future. For the system evolution, future profilescan also be multiplexed with the existing profiles in a single RFchannel through a future extension frame (FEF). The details of each PHYprofile are described below.

1. Base Profile

The base profile represents a main use case for fixed receiving devicesthat are usually connected to a roof-top antenna. The base profile alsoincludes portable devices that could be transported to a place butbelong to a relatively stationary reception category. Use of the baseprofile could be extended to handheld devices or even vehicular by someimproved implementations, but those use cases are not expected for thebase profile receiver operation.

Target SNR range of reception is from approximately 10 to 20 dB, whichincludes the 15 dB SNR reception capability of the existing broadcastsystem (e.g. ATSC A/53). The receiver complexity and power consumptionis not as critical as in the battery-operated handheld devices, whichwill use the handheld profile. Key system parameters for the baseprofile are listed in below table 1.

TABLE 1 LDPC codeword length 16K, 64K bits Constellation size 4~10 bpcu(bits per channel use) Time de-interleaving memory size ≤2¹⁹ data cellsPilot patterns Pilot pattern for fixed reception FFT size 16K, 32Kpoints

2. Handheld Profile

The handheld profile is designed for use in handheld and vehiculardevices that operate with battery power. The devices can be moving withpedestrian or vehicle speed. The power consumption as well as thereceiver complexity is very important for the implementation of thedevices of the handheld profile. The target SNR range of the handheldprofile is approximately 0 to 10 dB, but can be configured to reachbelow 0 dB when intended for deeper indoor reception.

In addition to low SNR capability, resilience to the Doppler Effectcaused by receiver mobility is the most important performance attributeof the handheld profile. Key system parameters for the handheld profileare listed in the below table 2.

TABLE 2 LDPC codeword length 16K bits Constellation size 2~8 bpcu Timede-interleaving ≤2¹⁸ data cells memory size Pilot patterns Pilotpatterns for mobile and indoor reception FFT size 8K, 16K points

3. Advanced Profile

The advanced profile provides highest channel capacity at the cost ofmore implementation complexity. This profile requires using MIMOtransmission and reception, and UHDTV service is a target use case forwhich this profile is specifically designed. The increased capacity canalso be used to allow an increased number of services in a givenbandwidth, e.g., multiple SDTV or HDTV services.

The target SNR range of the advanced profile is approximately 20 to 30dB. MIMO transmission may initially use existing elliptically-polarizedtransmission equipment, with extension to full-power cross-polarizedtransmission in the future. Key system parameters for the advancedprofile are listed in below table 3.

TABLE 3 LDPC codeword length 16K, 64K bits Constellation size 8~12 bpcuTime de-interleaving memory size ≤2¹⁹ data cells Pilot patterns Pilotpattern for fixed reception FFT size 16K, 32K points

In this case, the base profile can be used as a profile for both theterrestrial broadcast service and the mobile broadcast service. That is,the base profile can be used to define a concept of a profile whichincludes the mobile profile. Also, the advanced profile can be dividedadvanced profile for a base profile with MIMO and advanced profile for ahandheld profile with MIMO. Moreover, the three profiles can be changedaccording to intention of the designer.

The following terms and definitions may apply to the present invention.The following terms and definitions can be changed according to design.

auxiliary stream: sequence of cells carrying data of as yet undefinedmodulation and coding, which may be used for future extensions or asrequired by broadcasters or network operators.

base data pipe: data pipe that carries service signaling data.

baseband frame (or BBFRAME): set of Kbch bits which form the input toone FEC encoding process (BCH and LDPC encoding).

cell: modulation value that is carried by one carrier of the OFDMtransmission.

coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encodedblocks of PLS2 data.

data pipe: logical channel in the physical layer that carries servicedata or related metadata, which may carry one or multiple service(s) orservice component(s).

data pipe unit: a basic unit for allocating data cells to a DP in aframe.

data symbol: OFDM symbol in a frame which is not a preamble symbol (theframe signaling symbol and frame edge symbol is included in the datasymbol).

DP_ID: this 8-bit field identifies uniquely a DP within the systemidentified by the SYSTEM_ID.

dummy cell: cell carrying a pseudo-random value used to fill theremaining capacity not used for PLS signaling, DPs or auxiliary streams.

emergency alert channel: part of a frame that carries EAS informationdata.

frame: physical layer time slot that starts with a preamble and endswith a frame edge symbol.

frame repetition unit: a set of frames belonging to same or differentphysical layer profile including a FEF, which is repeated eight times ina super-frame.

fast information channel: a logical channel in a frame that carries themapping information between a service and the corresponding base DP.

FECBLOCK: set of LDPC-encoded bits of a DP data.

FFT size: nominal FFT size used for a particular mode, equal to theactive symbol period Ts expressed in cycles of the elementary period T.

frame signaling symbol: OFDM symbol with higher pilot density used atthe start of a frame in certain combinations of FFT size, guard intervaland scattered pilot pattern, which carries a part of the PLS data.

frame edge symbol: OFDM symbol with higher pilot density used at the endof a frame in certain combinations of FFT size, guard interval andscattered pilot pattern.

frame-group: the set of all the frames having the same PHY profile typein a super-frame.

future extension frame: physical layer time slot within the super-framethat could be used for future extension, which starts with a preamble.

Futurecast UTB system: proposed physical layer broadcasting system, ofwhich the input is one or more MPEG2-TS or IP or general stream(s) andof which the output is an RF signal.

input stream: A stream of data for an ensemble of services delivered tothe end users by the system.

normal data symbol: data symbol excluding the frame signaling symbol andthe frame edge symbol.

PHY profile: subset of all configurations that a corresponding receivershould implement.

PLS: physical layer signaling data consisting of PLS1 and PLS2.

PLS1: a first set of PLS data carried in the FSS symbols having a fixedsize, coding and modulation, which carries basic information about thesystem as well as the parameters needed to decode the PLS2.

NOTE: PLS1 data remains constant for the duration of a frame-group.

PLS2: a second set of PLS data transmitted in the FSS symbol, whichcarries more detailed PLS data about the system and the DPs.

PLS2 dynamic data: PLS2 data that may dynamically change frame-by-frame.

PLS2 static data: PLS2 data that remains static for the duration of aframe-group.

preamble signaling data: signaling data carried by the preamble symboland used to identify the basic mode of the system.

preamble symbol: fixed-length pilot symbol that carries basic PLS dataand is located in the beginning of a frame.

NOTE: The preamble symbol is mainly used for fast initial band scan todetect the system signal, its timing, frequency offset, and FFT-size.

reserved for future use: not defined by the present document but may bedefined in future.

super-frame: set of eight frame repetition units.

time interleaving block (TI block): set of cells within which timeinterleaving is carried out, corresponding to one use of the timeinterleaver memory.

TI group: unit over which dynamic capacity allocation for a particularDP is carried out, made up of an integer, dynamically varying number ofXFECBLOCKs.

NOTE: The TI group may be mapped directly to one frame or may be mappedto multiple frames. It may contain one or more TI blocks.

Type 1 DP: DP of a frame where all DPs are mapped into the frame in TDMfashion.

Type 2 DP: DP of a frame where all DPs are mapped into the frame in FDMfashion.

XFECBLOCK: set of Ncells cells carrying all the bits of one LDPCFECBLOCK.

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention.

The apparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can includean input formatting block 1000, a BICM (Bit interleaved coding &modulation) block 1010, a frame building block 1020, an OFDM (OrthogonalFrequency Division Multiplexing) generation block 1030 and a signalinggeneration block 1040. A description will be given of the operation ofeach module of the apparatus for transmitting broadcast signals.

IP stream/packets and MPEG2-TS are the main input formats, other streamtypes are handled as General Streams. In addition to these data inputs,Management Information is input to control the scheduling and allocationof the corresponding bandwidth for each input stream. One or multiple TSstream(s), IP stream(s) and/or General Stream(s) inputs aresimultaneously allowed.

The input formatting block 1000 can demultiplex each input stream intoone or multiple data pipe(s), to each of which an independent coding andmodulation is applied. The data pipe (DP) is the basic unit forrobustness control, thereby affecting quality-of-service (QoS). One ormultiple service(s) or service component(s) can be carried by a singleDP. Details of operations of the input formatting block 1000 will bedescribed later.

The data pipe is a logical channel in the physical layer that carriesservice data or related metadata, which may carry one or multipleservice(s) or service component(s).

Also, the data pipe unit: a basic unit for allocating data cells to a DPin a frame.

In the BICM block 1010, parity data is added for error correction andthe encoded bit streams are mapped to complex-value constellationsymbols. The symbols are interleaved across a specific interleavingdepth that is used for the corresponding DP. For the advanced profile,MIMO encoding is performed in the BICM block 1010 and the additionaldata path is added at the output for MIMO transmission. Details ofoperations of the BICM block 1010 will be described later.

The Frame Building block 1020 can map the data cells of the input DPsinto the OFDM symbols within a frame. After mapping, the frequencyinterleaving is used for frequency-domain diversity, especially tocombat frequency-selective fading channels. Details of operations of theFrame Building block 1020 will be described later.

After inserting a preamble at the beginning of each frame, the OFDMGeneration block 1030 can apply conventional OFDM modulation having acyclic prefix as guard interval. For antenna space diversity, adistributed MISO scheme is applied across the transmitters. In addition,a Peak-to-Average Power Reduction (PAPR) scheme is performed in the timedomain. For flexible network planning, this proposal provides a set ofvarious FFT sizes, guard interval lengths and corresponding pilotpatterns. Details of operations of the OFDM Generation block 1030 willbe described later.

The Signaling Generation block 1040 can create physical layer signalinginformation used for the operation of each functional block. Thissignaling information is also transmitted so that the services ofinterest are properly recovered at the receiver side. Details ofoperations of the Signaling Generation block 1040 will be describedlater.

FIGS. 2, 3 and 4 illustrate the input formatting block 1000 according toembodiments of the present invention. A description will be given ofeach figure.

FIG. 2 illustrates an input formatting block according to one embodimentof the present invention. FIG. 2 shows an input formatting module whenthe input signal is a single input stream.

The input formatting block illustrated in FIG. 2 corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

The input to the physical layer may be composed of one or multiple datastreams. Each data stream is carried by one DP. The mode adaptationmodules slice the incoming data stream into data fields of the basebandframe (BBF). The system supports three types of input data streams:MPEG2-TS, Internet protocol (IP) and Generic stream (GS). MPEG2-TS ischaracterized by fixed length (188 byte) packets with the first bytebeing a sync-byte (0x47). An IP stream is composed of variable length IPdatagram packets, as signaled within IP packet headers. The systemsupports both IPv4 and IPv6 for the IP stream. GS may be composed ofvariable length packets or constant length packets, signaled withinencapsulation packet headers.

(a) shows a mode adaptation block 2000 and a stream adaptation 2010 forsignal DP and (b) shows a PLS generation block 2020 and a PLS scrambler2030 for generating and processing PLS data. A description will be givenof the operation of each block.

The Input Stream Splitter splits the input TS, IP, GS streams intomultiple service or service component (audio, video, etc.) streams. Themode adaptation module 2010 is comprised of a CRC Encoder, BB (baseband)Frame Slicer, and BB Frame Header Insertion block.

The CRC Encoder provides three kinds of CRC encoding for error detectionat the user packet (UP) level, i.e., CRC-8, CRC-16, and CRC-32. Thecomputed CRC bytes are appended after the UP. CRC-8 is used for TSstream and CRC-32 for IP stream. If the GS stream doesn't provide theCRC encoding, the proposed CRC encoding should be applied.

BB Frame Slicer maps the input into an internal logical-bit format. Thefirst received bit is defined to be the MSB. The BB Frame Slicerallocates a number of input bits equal to the available data fieldcapacity. To allocate a number of input bits equal to the BBF payload,the UP packet stream is sliced to fit the data field of BBF.

BB Frame Header Insertion block can insert fixed length BBF header of 2bytes is inserted in front of the BB Frame. The BBF header is composedof STUFFI (1 bit), SYNCD (13 bits), and RFU (2 bits). In addition to thefixed 2-Byte BBF header, BBF can have an extension field (1 or 3 bytes)at the end of the 2-byte BBF header.

The stream adaptation 2010 is comprised of stuffing insertion block andBB scrambler. The stuffing insertion block can insert stuffing fieldinto a payload of a BB frame. If the input data to the stream adaptationis sufficient to fill a BB-Frame, STUFFI is set to ‘0’ and the BBF hasno stuffing field. Otherwise STUFFI is set to ‘1’ and the stuffing fieldis inserted immediately after the BBF header. The stuffing fieldcomprises two bytes of the stuffing field header and a variable size ofstuffing data.

The BB scrambler scrambles complete BBF for energy dispersal. Thescrambling sequence is synchronous with the BBF. The scrambling sequenceis generated by the feed-back shift register.

The PLS generation block 2020 can generate physical layer signaling(PLS) data. The PLS provides the receiver with a means to accessphysical layer DPs. The PLS data consists of PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in the FSS symbols inthe frame having a fixed size, coding and modulation, which carriesbasic information about the system as well as the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable the reception anddecoding of the PLS2 data. Also, the PLS1 data remains constant for theduration of a frame-group.

The PLS2 data is a second set of PLS data transmitted in the FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode the desired DP. The PLS2 signaling further consistsof two types of parameters, PLS2 Static data (PLS2-STAT data) and PLS2dynamic data (PLS2-DYN data). The PLS2 Static data is PLS2 data thatremains static for the duration of a frame-group and the PLS2 dynamicdata is PLS2 data that may dynamically change frame-by-frame.

Details of the PLS data will be described later.

The PLS scrambler 2030 can scramble the generated PLS data for energydispersal.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 3 illustrates an input formatting block according to anotherembodiment of the present invention.

The input formatting block illustrated in FIG. 3 corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

FIG. 3 shows a mode adaptation block of the input formatting block whenthe input signal corresponds to multiple input streams.

The mode adaptation block of the input formatting block for processingthe multiple input streams can independently process the multiple inputstreams.

Referring to FIG. 3, the mode adaptation block for respectivelyprocessing the multiple input streams can include an input streamsplitter 3000, an input stream synchronizer 3010, a compensating delayblock 3020, a null packet deletion block 3030, a head compression block3040, a CRC encoder 3050, a BB frame slicer 3060 and a BB headerinsertion block 3070. Description will be given of each block of themode adaptation block.

Operations of the CRC encoder 3050, BB frame slicer 3060 and BB headerinsertion block 3070 correspond to those of the CRC encoder, BB frameslicer and BB header insertion block described with reference to FIG. 2and thus description thereof is omitted.

The input stream splitter 3000 can split the input TS, IP, GS streamsinto multiple service or service component (audio, video, etc.) streams.

The input stream synchronizer 3010 may be referred as ISSY. The ISSY canprovide suitable means to guarantee Constant Bit Rate (CBR) and constantend-to-end transmission delay for any input data format. The ISSY isalways used for the case of multiple DPs carrying TS, and optionallyused for multiple DPs carrying GS streams.

The compensating delay block 3020 can delay the split TS packet streamfollowing the insertion of ISSY information to allow a TS packetrecombining mechanism without requiring additional memory in thereceiver.

The null packet deletion block 3030, is used only for the TS inputstream case. Some TS input streams or split TS streams may have a largenumber of null-packets present in order to accommodate VBR (variablebit-rate) services in a CBR TS stream. In this case, in order to avoidunnecessary transmission overhead, null-packets can be identified andnot transmitted. In the receiver, removed null-packets can bere-inserted in the exact place where they were originally by referenceto a deleted null-packet (DNP) counter that is inserted in thetransmission, thus guaranteeing constant bit-rate and avoiding the needfor time-stamp (PCR) updating.

The head compression block 3040 can provide packet header compression toincrease transmission efficiency for TS or IP input streams. Because thereceiver can have a priori information on certain parts of the header,this known information can be deleted in the transmitter.

For Transport Stream, the receiver has a-priori information about thesync-byte configuration (0x47) and the packet length (188 Byte). If theinput TS stream carries content that has only one PID, i.e., for onlyone service component (video, audio, etc.) or service sub-component (SVCbase layer, SVC enhancement layer, MVC base view or MVC dependentviews), TS packet header compression can be applied (optionally) to theTransport Stream. IP packet header compression is used optionally if theinput steam is an IP stream. The above-described blocks may be omittedor replaced by blocks having similar or identical functions.

FIG. 4 illustrates a BICM block according to an embodiment of thepresent invention.

The BICM block illustrated in FIG. 4 corresponds to an embodiment of theBICM block 1010 described with reference to FIG. 1.

As described above, the apparatus for transmitting broadcast signals forfuture broadcast services according to an embodiment of the presentinvention can provide a terrestrial broadcast service, mobile broadcastservice, UHDTV service, etc.

Since QoS (quality of service) depends on characteristics of a serviceprovided by the apparatus for transmitting broadcast signals for futurebroadcast services according to an embodiment of the present invention,data corresponding to respective services needs to be processed throughdifferent schemes. Accordingly, the a BICM block according to anembodiment of the present invention can independently process DPs inputthereto by independently applying SISO, MISO and MIMO schemes to thedata pipes respectively corresponding to data paths. Consequently, theapparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can controlQoS for each service or service component transmitted through each DP.

(a) shows the BICM block shared by the base profile and the handheldprofile and (b) shows the BICM block of the advanced profile.

The BICM block shared by the base profile and the handheld profile andthe BICM block of the advanced profile can include plural processingblocks for processing each DP.

A description will be given of each processing block of the BICM blockfor the base profile and the handheld profile and the BICM block for theadvanced profile.

A processing block 5000 of the BICM block for the base profile and thehandheld profile can include a Data FEC encoder 5010, a bit interleaver5020, a constellation mapper 5030, an SSD (Signal Space Diversity)encoding block 5040 and a time interleaver 5050.

The Data FEC encoder 5010 can perform the FEC encoding on the input BBFto generate FECBLOCK procedure using outer coding (BCH), and innercoding (LDPC). The outer coding (BCH) is optional coding method. Detailsof operations of the Data FEC encoder 5010 will be described later.

The bit interleaver 5020 can interleave outputs of the Data FEC encoder5010 to achieve optimized performance with combination of the LDPC codesand modulation scheme while providing an efficiently implementablestructure. Details of operations of the bit interleaver 5020 will bedescribed later.

The constellation mapper 5030 can modulate each cell word from the bitinterleaver 5020 in the base and the handheld profiles, or cell wordfrom the Cell-word demultiplexer 5010-1 in the advanced profile usingeither QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) ornon-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024) to give apower-normalized constellation point, el. This constellation mapping isapplied only for DPs. Observe that QAM-16 and NUQs are square shaped,while NUCs have arbitrary shape. When each constellation is rotated byany multiple of 90 degrees, the rotated constellation exactly overlapswith its original one. This “rotation-sense” symmetric property makesthe capacities and the average powers of the real and imaginarycomponents equal to each other. Both NUQs and NUCs are definedspecifically for each code rate and the particular one used is signaledby the parameter DP_MOD filed in PLS2 data.

The time interleaver 5050 can operates at the DP level. The parametersof time interleaving (TI) may be set differently for each DP. Details ofoperations of the time interleaver 5050 will be described later.

A processing block 50001 of the BICM block for the advanced profile caninclude the Data FEC encoder, bit interleaver, constellation mapper, andtime interleaver.

However, the processing block 5000-1 is distinguished from theprocessing block 5000 further includes a cell-word demultiplexer 50101and a MIMO encoding block 50201.

Also, the operations of the Data FEC encoder, bit interleaver,constellation mapper, and time interleaver in the processing block5000-1 correspond to those of the Data FEC encoder 5010, bit interleaver5020, constellation mapper 5030, and time interleaver 5050 described andthus description thereof is omitted.

The cell-word demultiplexer 5010-1 is used for the DP of the advancedprofile to divide the single cell-word stream into dual cell-wordstreams for MIMO processing. Details of operations of the cell-worddemultiplexer 5010-1 will be described later.

The MIMO encoding block 5020-1 can processing the output of thecell-word demultiplexer 5010-1 using MIMO encoding scheme. The MIMOencoding scheme was optimized for broadcasting signal transmission. TheMIMO technology is a promising way to get a capacity increase but itdepends on channel characteristics. Especially for broadcasting, thestrong LOS component of the channel or a difference in the receivedsignal power between two antennas caused by different signal propagationcharacteristics makes it difficult to get capacity gain from MIMO. Theproposed MIMO encoding scheme overcomes this problem using arotation-based pre-coding and phase randomization of one of the MIMOoutput signals.

MIMO encoding is intended for a 2×2 MIMO system requiring at least twoantennas at both the transmitter and the receiver. Two MIMO encodingmodes are defined in this proposal; full-rate spatial multiplexing(FR-SM) and full-rate full-diversity spatial multiplexing (FRFD-SM). TheFR-SM encoding provides capacity increase with relatively smallcomplexity increase at the receiver side while the FRFD-SM encodingprovides capacity increase and additional diversity gain with a greatcomplexity increase at the receiver side. The proposed MIMO encodingscheme has no restriction on the antenna polarity configuration.

MIMO processing is required for the advanced profile frame, which meansall DPs in the advanced profile frame are processed by the MIMO encoder.MIMO processing is applied at DP level. Pairs of the ConstellationMapper outputs NUQ (e1,i and e2,i) are fed to the input of the MIMOEncoder. Paired MIMO Encoder output (g1,i and g2,i) is transmitted bythe same carrier k and OFDM symbol 1 of their respective TX antennas.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 5 illustrates a BICM block according to another embodiment of thepresent invention.

The BICM block illustrated in FIG. 6 corresponds to an embodiment of theBICM block 1010 described with reference to FIG. 1.

FIG. 5 illustrates a BICM block for protection of physical layersignaling (PLS), emergency alert channel (EAC) and fast informationchannel (FIC). EAC is a part of a frame that carries EAS informationdata and FIC is a logical channel in a frame that carries the mappinginformation between a service and the corresponding base DP. Details ofthe EAC and FIC will be described later.

Referring to FIG. 6, the BICM block for protection of PLS, EAC and FICcan include a PLS FEC encoder 6000, a bit interleaver 6010 and aconstellation mapper 6020.

Also, the PLS FEC encoder 6000 can include a scrambler, BCHencoding/zero insertion block, LDPC encoding block and LDPC paritypuncturing block. Description will be given of each block of the BICMblock.

The PLS FEC encoder 6000 can encode the scrambled PLS 1/2 data, EAC andFIC section.

The scrambler can scramble PLS1 data and PLS2 data before BCH encodingand shortened and punctured LDPC encoding.

The BCH encoding/zero insertion block can perform outer encoding on thescrambled PLS 1/2 data using the shortened BCH code for PLS protectionand insert zero bits after the BCH encoding. For PLS1 data only, theoutput bits of the zero insertion may be permuted before LDPC encoding.

The LDPC encoding block can encode the output of the BCH encoding/zeroinsertion block using LDPC code. To generate a complete coded block,Cldpc, parity bits, Pldpc are encoded systematically from eachzero-inserted PLS information block, Ildpc and appended after it.

C _(lpdc)=[I _(lpdc) P _(ldpc)]=[i ₀ ,i ₁ , . . . ,i _(K) _(lpdc) ⁻¹ ,p₀ ,p ₁ , . . . ,p _(N) _(lpdc) _(−K) _(lpdc) ⁻¹]  [Equation 1]

The LDPC code parameters for PLS1 and PLS2 are as following table 4.

TABLE 4 Signaling Type K_(sig) K_(bch) N_(bch)_parity K_(ldpc)(=N_(bch)) N_(ldpc) N_(ldpc)_parity code rate Q_(ldpc) PLS1 342 1020 601080 4320 3240 1/4  36 PLS2 <1021 >1020 2100 2160 7200 5040 3/10 56

The LDPC parity puncturing block can perform puncturing on the PLS1 dataand PLS 2 data.

When shortening is applied to the PLS1 data protection, some LDPC paritybits are punctured after LDPC encoding. Also, for the PLS2 dataprotection, the LDPC parity bits of PLS2 are punctured after LDPCencoding. These punctured bits are not transmitted.

The bit interleaver 6010 can interleave the each shortened and puncturedPLS1 data and PLS2 data.

The constellation mapper 6020 can map the bit interleaved PLS1 data andPLS2 data onto constellations.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 6 illustrates a frame building block according to one embodiment ofthe present invention.

The frame building block illustrated in FIG. 6 corresponds to anembodiment of the frame building block 1020 described with reference toFIG. 1.

Referring to FIG. 6, the frame building block can include a delaycompensation block 7000, a cell mapper 7010 and a frequency interleaver7020. Description will be given of each block of the frame buildingblock.

The delay compensation block 7000 can adjust the timing between the datapipes and the corresponding PLS data to ensure that they are co-timed atthe transmitter end. The PLS data is delayed by the same amount as datapipes are by addressing the delays of data pipes caused by the InputFormatting block and BICM block. The delay of the BICM block is mainlydue to the time interleaver 5050. In-band signaling data carriesinformation of the next TI group so that they are carried one frameahead of the DPs to be signaled. The Delay Compensating block delaysin-band signaling data accordingly.

The cell mapper 7010 can map PLS, EAC, FIC, DPs, auxiliary streams anddummy cells into the active carriers of the OFDM symbols in the frame.The basic function of the cell mapper 7010 is to map data cells producedby the TIs for each of the DPs, PLS cells, and EAC/FIC cells, if any,into arrays of active OFDM cells corresponding to each of the OFDMsymbols within a frame. Service signaling data (such as PSI (programspecific information)/SI) can be separately gathered and sent by a datapipe. The Cell Mapper operates according to the dynamic informationproduced by the scheduler and the configuration of the frame structure.Details of the frame will be described later.

The frequency interleaver 7020 can randomly interleave data cellsreceived from the cell mapper 7010 to provide frequency diversity. Also,the frequency interleaver 7020 can operate on very OFDM symbol paircomprised of two sequential OFDM symbols using a differentinterleaving-seed order to get maximum interleaving gain in a singleframe.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 7 illustrates an OFDM generation block according to an embodimentof the present invention.

The OFDM generation block illustrated in FIG. 7 corresponds to anembodiment of the OFDM generation block 1030 described with reference toFIG. 1.

The OFDM generation block modulates the OFDM carriers by the cellsproduced by the Frame Building block, inserts the pilots, and producesthe time domain signal for transmission. Also, this block subsequentlyinserts guard intervals, and applies PAPR (Peak-to-Average Power Radio)reduction processing to produce the final RF signal.

Referring to FIG. 7, the OFDM generation block can include a pilot andreserved tone insertion block 8000, a 2D-eSFN encoding block 8010, anIFFT (Inverse Fast Fourier Transform) block 8020, a PAPR reduction block8030, a guard interval insertion block 8040, a preamble insertion block8050, other system insertion block 8060 and a DAC block 8070.

The other system insertion block 8060 can multiplex signals of aplurality of broadcast transmission/reception systems in the time domainsuch that data of two or more different broadcast transmission/receptionsystems providing broadcast services can be simultaneously transmittedin the same RF signal bandwidth. In this case, the two or more differentbroadcast transmission/reception systems refer to systems providingdifferent broadcast services. The different broadcast services may referto a terrestrial broadcast service, mobile broadcast service, etc.

FIG. 8 illustrates a structure of an apparatus for receiving broadcastsignals for future broadcast services according to an embodiment of thepresent invention.

The apparatus for receiving broadcast signals for future broadcastservices according to an embodiment of the present invention cancorrespond to the apparatus for transmitting broadcast signals forfuture broadcast services, described with reference to FIG. 1.

The apparatus for receiving broadcast signals for future broadcastservices according to an embodiment of the present invention can includea synchronization & demodulation module 9000, a frame parsing module9010, a demapping & decoding module 9020, an output processor 9030 and asignaling decoding module 9040. A description will be given of operationof each module of the apparatus for receiving broadcast signals.

The synchronization & demodulation module 9000 can receive input signalsthrough m Rx antennas, perform signal detection and synchronization withrespect to a system corresponding to the apparatus for receivingbroadcast signals and carry out demodulation corresponding to a reverseprocedure of the procedure performed by the apparatus for transmittingbroadcast signals.

The frame parsing module 9010 can parse input signal frames and extractdata through which a service selected by a user is transmitted. If theapparatus for transmitting broadcast signals performs interleaving, theframe parsing module 9010 can carry out deinterleaving corresponding toa reverse procedure of interleaving. In this case, the positions of asignal and data that need to be extracted can be obtained by decodingdata output from the signaling decoding module 9040 to restorescheduling information generated by the apparatus for transmittingbroadcast signals.

The demapping & decoding module 9020 can convert the input signals intobit domain data and then deinterleave the same as necessary. Thedemapping & decoding module 9020 can perform demapping for mappingapplied for transmission efficiency and correct an error generated on atransmission channel through decoding. In this case, the demapping &decoding module 9020 can obtain transmission parameters necessary fordemapping and decoding by decoding the data output from the signalingdecoding module 9040.

The output processor 9030 can perform reverse procedures of variouscompression/signal processing procedures which are applied by theapparatus for transmitting broadcast signals to improve transmissionefficiency. In this case, the output processor 9030 can acquirenecessary control information from data output from the signalingdecoding module 9040. The output of the output processor 8300corresponds to a signal input to the apparatus for transmittingbroadcast signals and may be MPEG-TSs, IP streams (v4 or v6) and genericstreams.

The signaling decoding module 9040 can obtain PLS information from thesignal demodulated by the synchronization & demodulation module 9000. Asdescribed above, the frame parsing module 9010, demapping & decodingmodule 9020 and output processor 9030 can execute functions thereofusing the data output from the signaling decoding module 9040.

FIG. 9 illustrates a frame structure according to an embodiment of thepresent invention.

FIG. 9 shows an example configuration of the frame types and FRUs in asuper-frame. (a) shows a super frame according to an embodiment of thepresent invention, (b) shows FRU (Frame Repetition Unit) according to anembodiment of the present invention, (c) shows frames of variable PHYprofiles in the FRU and (d) shows a structure of a frame.

A super-frame may be composed of eight FRUs. The FRU is a basicmultiplexing unit for TDM of the frames, and is repeated eight times ina super-frame.

Each frame in the FRU belongs to one of the PHY profiles, (base,handheld, advanced) or FEF. The maximum allowed number of the frames inthe FRU is four and a given PHY profile can appear any number of timesfrom zero times to four times in the FRU (e.g., base, base, handheld,advanced). PHY profile definitions can be extended using reserved valuesof the PHY_PROFILE in the preamble, if required.

The FEF part is inserted at the end of the FRU, if included. When theFEF is included in the FRU, the minimum number of FEFs is 8 in asuper-frame. It is not recommended that FEF parts be adjacent to eachother.

One frame is further divided into a number of OFDM symbols and apreamble. As shown in (d), the frame comprises a preamble, one or moreframe signaling symbols (FSS), normal data symbols and a frame edgesymbol (FES).

The preamble is a special symbol that enables fast Futurecast UTB systemsignal detection and provides a set of basic transmission parameters forefficient transmission and reception of the signal. The detaileddescription of the preamble will be will be described later.

The main purpose of the FSS(s) is to carry the PLS data. For fastsynchronization and channel estimation, and hence fast decoding of PLSdata, the FSS has more dense pilot pattern than the normal data symbol.The FES has exactly the same pilots as the FSS, which enablesfrequency-only interpolation within the FES and temporal interpolation,without extrapolation, for symbols immediately preceding the FES.

FIG. 10 illustrates a signaling hierarchy structure of the frameaccording to an embodiment of the present invention.

FIG. 10 illustrates the signaling hierarchy structure, which is splitinto three main parts: the preamble signaling data 11000, the PLS1 data11010 and the PLS2 data 11020. The purpose of the preamble, which iscarried by the preamble symbol in every frame, is to indicate thetransmission type and basic transmission parameters of that frame. ThePLS1 enables the receiver to access and decode the PLS2 data, whichcontains the parameters to access the DP of interest. The PLS2 iscarried in every frame and split into two main parts: PLS2-STAT data andPLS2-DYN data. The static and dynamic portion of PLS2 data is followedby padding, if necessary.

FIG. 11 illustrates preamble signaling data according to an embodimentof the present invention.

Preamble signaling data carries 21 bits of information that are neededto enable the receiver to access PLS data and trace DPs within the framestructure. Details of the preamble signaling data are as follows:

PHY_PROFILE: This 3-bit field indicates the PHY profile type of thecurrent frame. The mapping of different PHY profile types is given inbelow table 5.

TABLE 5 Value PHY profile 000 Base profile 001 Handheld profile 010Advanced profiled 011~110 Reserved 111 FEF

FFT_SIZE: This 2 bit field indicates the FFT size of the current framewithin a frame-group, as described in below table 6.

TABLE 6 Value FFT size 00  8K FFT 01 16K FFT 10 32K FFT 11 Reserved

GI_FRACTION: This 3 bit field indicates the guard interval fractionvalue in the current super-frame, as described in below table 7.

TABLE 7 Value GI_FRACTION 000 1/5  001 1/10 010 1/20 011 1/40 100 1/80101  1/160 110~111 Reserved

EAC_FLAG: This 1 bit field indicates whether the EAC is provided in thecurrent frame. If this field is set to ‘1’, emergency alert service(EAS) is provided in the current frame. If this field set to ‘0’, EAS isnot carried in the current frame. This field can be switched dynamicallywithin a super-frame.

PILOT_MODE: This 1-bit field indicates whether the pilot mode is mobilemode or fixed mode for the current frame in the current frame-group. Ifthis field is set to ‘0’, mobile pilot mode is used. If the field is setto ‘1’, the fixed pilot mode is used.

PAPR_FLAG: This 1-bit field indicates whether PAPR reduction is used forthe current frame in the current frame-group. If this field is set tovalue ‘1’, tone reservation is used for PAPR reduction. If this field isset to ‘0’, PAPR reduction is not used.

FRU_CONFIGURE: This 3-bit field indicates the PHY profile typeconfigurations of the frame repetition units (FRU) that are present inthe current super-frame. All profile types conveyed in the currentsuper-frame are identified in this field in all preambles in the currentsuper-frame. The 3-bit field has a different definition for eachprofile, as show in below table 8.

TABLE 8 Current Current Current PHY_PROFILE PHY_PROFILE CurrentPHY_PROFILE = ‘001’ ‘010’ PHY_PROFILE = ‘000’ (base) (handheld)(advanced) ‘111’ (FEF) FRU_CONFIGURE = Only base Only handheld Onlyadvanced Only FEF 000 profile present profile present profile presentpresent FRU_CONFIGURE = Handheld Base profile Base profile Base profile1XX profile present present present present FRU_CONFIGURE = AdvancedAdvanced Handheld Handheld X1X profile profile profile profile presentpresent present present FRU_CONFIGURE = FEF FEF FEF Advanced XX1 presentpresent present profile present

RESERVED: This 7-bit field is reserved for future use.

FIG. 12 illustrates PLS1 data according to an embodiment of the presentinvention.

PLS1 data provides basic transmission parameters including parametersrequired to enable the reception and decoding of the PLS2. As abovementioned, the PLS1 data remain unchanged for the entire duration of oneframe-group. The detailed definition of the signaling fields of the PLS1data are as follows:

PREAMBLE_DATA: This 20-bit field is a copy of the preamble signalingdata excluding the EAC_FLAG.

NUM_FRAME_FRU: This 2-bit field indicates the number of the frames perFRU.

PAYLOAD_TYPE: This 3-bit field indicates the format of the payload datacarried in the frame-group. PAYLOAD_TYPE is signaled as shown in table9.

TABLE 9 value Payload type 1XX TS stream is transmitted X1X IP stream istransmitted XX1 GS stream is transmitted

NUM_FSS: This 2-bit field indicates the number of FSS symbols in thecurrent frame.

SYSTEM_VERSION: This 8-bit field indicates the version of thetransmitted signal format. The SYSTEM_VERSION is divided into two 4-bitfields, which are a major version and a minor version.

Major version: The MSB four bits of SYSTEM_VERSION field indicate majorversion information. A change in the major version field indicates anon-backward-compatible change. The default value is ‘0000’. For theversion described in this standard, the value is set to ‘0000’.

Minor version: The LSB four bits of SYSTEM_VERSION field indicate minorversion information. A change in the minor version field isbackward-compatible.

CELL_ID: This is a 16-bit field which uniquely identifies a geographiccell in an ATSC network. An ATSC cell coverage area may consist of oneor more frequencies, depending on the number of frequencies used perFuturecast UTB system. If the value of the CELL_ID is not known orunspecified, this field is set to ‘0’.

NETWORK_ID: This is a 16-bit field which uniquely identifies the currentATSC network.

SYSTEM_ID: This 16-bit field uniquely identifies the Futurecast UTBsystem within the ATSC network. The Futurecast UTB system is theterrestrial broadcast system whose input is one or more input streams(TS, IP, GS) and whose output is an RF signal. The Futurecast UTB systemcarries one or more PHY profiles and FEF, if any. The same FuturecastUTB system may carry different input streams and use different RFfrequencies in different geographical areas, allowing local serviceinsertion. The frame structure and scheduling is controlled in one placeand is identical for all transmissions within a Futurecast UTB system.One or more Futurecast UTB systems may have the same SYSTEM_ID meaningthat they all have the same physical layer structure and configuration.

The following loop consists of FRU_PHY_PROFILE, FRU_FRAME_LENGTH,FRU_GI_FRACTION, and RESERVED which are used to indicate the FRUconfiguration and the length of each frame type. The loop size is fixedso that four PHY profiles (including a FEF) are signaled within the FRU.If NUM_FRAME_FRU is less than 4, the unused fields are filled withzeros.

FRU_PHY_PROFILE: This 3-bit field indicates the PHY profile type of the(i+1)th (i is the loop index) frame of the associated FRU. This fielduses the same signaling format as shown in the table 8.

FRU_FRAME_LENGTH: This 2-bit field indicates the length of the (i+1)thframe of the associated FRU. Using FRU_FRAME_LENGTH together withFRU_GI_FRACTION, the exact value of the frame duration can be obtained.

FRU_GI_FRACTION: This 3-bit field indicates the guard interval fractionvalue of the (i+1)th frame of the associated FRU. FRU_GI_FRACTION issignaled according to the table 7.

RESERVED: This 4-bit field is reserved for future use.

The following fields provide parameters for decoding the PLS2 data.

PLS2_FEC_TYPE: This 2-bit field indicates the FEC type used by the PLS2protection. The FEC type is signaled according to table 10. The detailsof the LDPC codes will be described later.

TABLE 10 Content PLS2 FEC type 00 4K-1/4 and 7K-3/10 LDPC codes 01~11Reserved

PLS2_MOD: This 3-bit field indicates the modulation type used by thePLS2. The modulation type is signaled according to table 11.

TABLE 11 Value PLS2_MODE 000 BPSK 001 QPSK 010 QAM-16 011 NUQ-64 100~111Reserved

PLS2_SIZE_CELL: This 15-bit field indicates Ctotal_partial_block, thesize (specified as the number of QAM cells) of the collection of fullcoded blocks for PLS2 that is carried in the current frame-group. Thisvalue is constant during the entire duration of the current frame-group.

PLS2_STAT_SIZE_BIT: This 14-bit field indicates the size, in bits, ofthe PLS2-STAT for the current frame-group. This value is constant duringthe entire duration of the current frame-group.

PLS2_DYN_SIZE_BIT: This 14-bit field indicates the size, in bits, of thePLS2-DYN for the current frame-group. This value is constant during theentire duration of the current frame-group.

PLS2_REP_FLAG: This 1-bit flag indicates whether the PLS2 repetitionmode is used in the current frame-group. When this field is set to value‘1’, the PLS2 repetition mode is activated. When this field is set tovalue ‘0’, the PLS2 repetition mode is deactivated.

PLS2_REP_SIZE_CELL: This 15-bit field indicates Ctotalpartial block, thesize (specified as the number of QAM cells) of the collection of partialcoded blocks for PLS2 carried in every frame of the current frame-group,when PLS2 repetition is used. If repetition is not used, the value ofthis field is equal to 0. This value is constant during the entireduration of the current frame-group.

PLS2_NEXT_FEC_TYPE: This 2-bit field indicates the FEC type used forPLS2 that is carried in every frame of the next frame-group. The FECtype is signaled according to the table 10.

PLS2_NEXT_MOD: This 3-bit field indicates the modulation type used forPLS2 that is carried in every frame of the next frame-group. Themodulation type is signaled according to the table 11.

PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2repetition mode is used in the next frame-group. When this field is setto value ‘1’, the PLS2 repetition mode is activated. When this field isset to value ‘0’, the PLS2 repetition mode is deactivated.

PLS2_NEXT_REP_SIZE_CELL: This 15-bit field indicates Ctotal full block,The size (specified as the number of QAM cells) of the collection offull coded blocks for PLS2 that is carried in every frame of the nextframe-group, when PLS2 repetition is used. If repetition is not used inthe next frame-group, the value of this field is equal to 0. This valueis constant during the entire duration of the current frame-group.

PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-STAT for the next frame-group. This value is constantin the current frame-group.

PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-DYN for the next frame-group. This value is constantin the current frame-group.

PLS2_AP_MODE: This 2-bit field indicates whether additional parity isprovided for PLS2 in the current frame-group. This value is constantduring the entire duration of the current frame-group. The below table12 gives the values of this field. When this field is set to ‘00’,additional parity is not used for the PLS2 in the current frame-group.

TABLE 12 Value PLS2-AP mode 00 AP is not provided 01 AP1 mode 10~11Reserved

PLS2_AP_SIZE_CELL: This 15-bit field indicates the size (specified asthe number of QAM cells) of the additional parity bits of the PLS2. Thisvalue is constant during the entire duration of the current frame-group.

PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parityis provided for PLS2 signaling in every frame of next frame-group. Thisvalue is constant during the entire duration of the current frame-group.The table 12 defines the values of this field

PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates the size (specifiedas the number of QAM cells) of the additional parity bits of the PLS2 inevery frame of the next frame-group. This value is constant during theentire duration of the current frame-group.

RESERVED: This 32-bit field is reserved for future use.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS1 signaling.

FIG. 13 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 13 illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT dataare the same within a frame-group, while the PLS2-DYN data provideinformation that is specific for the current frame.

The details of fields of the PLS2-STAT data are as follows:

FIC_FLAG: This 1-bit field indicates whether the FIC is used in thecurrent frame-group. If this field is set to ‘1’, the FIC is provided inthe current frame. If this field set to ‘0’, the FIC is not carried inthe current frame. This value is constant during the entire duration ofthe current frame-group.

AUX_FLAG: This 1-bit field indicates whether the auxiliary stream(s) isused in the current frame-group. If this field is set to ‘1’, theauxiliary stream is provided in the current frame. If this field set to‘0’, the auxiliary stream is not carried in the current frame. Thisvalue is constant during the entire duration of current frame-group.

NUM_DP: This 6-bit field indicates the number of DPs carried within thecurrent frame. The value of this field ranges from 1 to 64, and thenumber of DPs is NUM_DP+1.

DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile.

DP_TYPE: This 3-bit field indicates the type of the DP. This is signaledaccording to the below table 13.

TABLE 13 Value DP Type 000 DP Type 1 001 DP Type 2 010~111 reserved

DP_GROUP_ID: This 8-bit field identifies the DP group with which thecurrent DP is associated. This can be used by a receiver to access theDPs of the service components associated with a particular service,which will have the same DP_GROUP_ID.

BASE_DP_ID: This 6-bit field indicates the DP carrying service signalingdata (such as PSI/SI) used in the Management layer. The DP indicated byBASE_DP_ID may be either a normal DP carrying the service signaling dataalong with the service data or a dedicated DP carrying only the servicesignaling data.

DP_FEC_TYPE: This 2-bit field indicates the FEC type used by theassociated DP. The FEC type is signaled according to the below table 14.

TABLE 14 Value FEC_TYPE 00 16K LDPC 01 64K LDPC 10~11 Reserved

DP_COD: This 4-bit field indicates the code rate used by the associatedDP. The code rate is signaled according to the below table 15.

TABLE 15 Value Code rate 0000 5/15 0001 6/15 0010 7/15 0011 8/15 01009/15 0101 10/15  0110 11/15  0111 12/15  1000 13/15  1001~1111 Reserved

DP_MOD: This 4-bit field indicates the modulation used by the associatedDP. The modulation is signaled according to the below table 16.

TABLE 16 Value Modulation 0000 QPSK 0001 QAM-16 0010 NUQ-64 0011 NUQ-2560100 NUQ-1024 0101 NUC-16 0110 NUC-64 0111 NUC-256 1000 NUC-10241001~1111 reserved

DP_SSD_FLAG: This 1-bit field indicates whether the SSD mode is used inthe associated DP. If this field is set to value ‘1’, SSD is used. Ifthis field is set to value ‘0’, SSD is not used.

The following field appears only if PHY_PROFILE is equal to ‘010’, whichindicates the advanced profile:

DP_MIMO: This 3-bit field indicates which type of MIMO encoding processis applied to the associated DP. The type of MIMO encoding process issignaled according to the table 17.

TABLE 17 Value MIMO encoding 000 FR-SM 001 FRFD-SM 010~111 reserved

DP_TI_TYPE: This 1-bit field indicates the type of time-interleaving. Avalue of ‘0’ indicates that one TI group corresponds to one frame andcontains one or more TI-blocks. A value of ‘1’ indicates that one TIgroup is carried in more than one frame and contains only one TI-block.

DP_TI_LENGTH: The use of this 2-bit field (the allowed values are only1, 2, 4, 8) is determined by the values set within the DP_TI_TYPE fieldas follows:

If the DP_TI_TYPE is set to the value ‘1’, this field indicates PI, thenumber of the frames to which each TI group is mapped, and there is oneTI-block per TI group (NTI=1). The allowed PI values with 2-bit fieldare defined in the below table 18.

If the DP_TI_TYPE is set to the value ‘0’, this field indicates thenumber of TI-blocks NTI per TI group, and there is one TI group perframe (PI=1). The allowed PI values with 2-bit field are defined in thebelow table 18.

TABLE 18 2-bit field P_(I) N_(TI) 00 1 1 01 2 2 10 4 3 11 8 4

DP_FRAME_INTERVAL: This 2-bit field indicates the frame interval (HUMP)within the frame-group for the associated DP and the allowed values are1, 2, 4, 8 (the corresponding 2-bit field is ‘00’, ‘01’, ‘10’, or ‘11’,respectively). For DPs that do not appear every frame of theframe-group, the value of this field is equal to the interval betweensuccessive frames. For example, if a DP appears on the frames 1, 5, 9,13, etc., this field is set to ‘4’. For DPs that appear in every frame,this field is set to ‘1’.

DP_TI_BYPASS: This 1-bit field determines the availability of timeinterleaver 5050. If time interleaving is not used for a DP, it is setto ‘1’. Whereas if time interleaving is used it is set to ‘0’.

DP_FIRST_FRAME_IDX: This 5-bit field indicates the index of the firstframe of the super-frame in which the current DP occurs. The value ofDP_FIRST_FRAME_IDX ranges from 0 to 31.

DP_NUM_BLOCK_MAX: This 10-bit field indicates the maximum value ofDP_NUM_BLOCKS for this DP. The value of this field has the same range asDP_NUM_BLOCKS.

DP_PAYLOAD_TYPE: This 2-bit field indicates the type of the payload datacarried by the given DP. DP_PAYLOAD_TYPE is signaled according to thebelow table 19.

TABLE 19 Value Payload Type 00 TS. 01 IP 10 GS 11 reserved

DP_INBAND_MODE: This 2-bit field indicates whether the current DPcarries in-band signaling information. The in-band signaling type issignaled according to the below table 20.

TABLE 20 Value In-band mode 00 In-band signaling is not carried. 01INBAND-PLS is carried only 10 INBAND-ISSY is carried only 11 INBAND-PLSand INBAND-ISSY are carried

DP_PROTOCOL_TYPE: This 2-bit field indicates the protocol type of thepayload carried by the given DP. It is signaled according to the belowtable 21 when input payload types are selected.

TABLE 21 If If If DP_PAY- DP_PAY- DP_PAY- LOAD_TYPE LOAD_TYPE LOAD_TYPEValue Is TS Is IP Is GS 00 MPEG2-TS IPv4 (Note) 01 Reserved IPv6Reserved 10 Reserved Reserved Reserved 11 Reserved Reserved Reserved

DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used inthe Input Formatting block. The CRC mode is signaled according to thebelow table 22.

TABLE 22 Value CRC mode 00 Not used 01 CRC-8 10 CRC-16 11 CRC-32

DNP_MODE: This 2-bit field indicates the null-packet deletion mode usedby the associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). DNP_MODEis signaled according to the below table 23. If DP_PAYLOAD_TYPE is notTS (‘00’), DNP_MODE is set to the value ‘00’.

TABLE 23 Value Null-packet deletion mode 00 Not used 01 DNP-NORMAL 10DNP-OFFSET 11 reserved

ISSY_MODE: This 2-bit field indicates the ISSY mode used by theassociated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). The ISSY_MODE issignaled according to the below table 24 If DP_PAYLOAD_TYPE is not TS(‘00’), ISSY_MODE is set to the value ‘00’.

TABLE 24 Value ISSY mode 00 Not used 01 ISSY-UP 10 ISSY-BBF 11 reserved

HC_MODE_TS: This 2-bit field indicates the TS header compression modeused by the associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). TheHC_MODE_TS is signaled according to the below table 25.

TABLE 25 Value Header compression mode 00 HC_MODE_TS 1 01 HC_MODE_TS 210 HC_MODE_TS 3 11 HC_MODE_TS 4

HC_MODE_IP: This 2-bit field indicates the IP header compression modewhen DP_PAYLOAD_TYPE is set to IP (‘01’). The HC_MODE_IP is signaledaccording to the below table 26.

TABLE 26 Value Header compression mode 00 No compression 01 HC_MODE_IP 110~11 reserved

PID: This 13-bit field indicates the PID number for TS headercompression when DP_PAYLOAD_TYPE is set to TS (‘00’) and HC_MODE_TS isset to ‘01’ or ‘10’.

RESERVED: This 8-bit field is reserved for future use.

The following field appears only if FIC_FLAG is equal to ‘1’:

FIC_VERSION: This 8-bit field indicates the version number of the FIC.

FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, ofthe FIC.

RESERVED: This 8-bit field is reserved for future use.

The following field appears only if AUX_FLAG is equal to ‘1’:

NUM_AUX: This 4-bit field indicates the number of auxiliary streams.Zero means no auxiliary streams are used.

AUX_CONFIG_RFU: This 8-bit field is reserved for future use.

AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicatingthe type of the current auxiliary stream.

AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use forsignaling auxiliary streams.

FIG. 14 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 14 illustrates PLS2-DYN data of the PLS2 data. The values of thePLS2-DYN data may change during the duration of one frame-group, whilethe size of fields remains constant.

The details of fields of the PLS2-DYN data are as follows:

FRAME_INDEX: This 5-bit field indicates the frame index of the currentframe within the super-frame. The index of the first frame of thesuper-frame is set to ‘0’.

PLS_CHANGE_COUNTER: This 4-bit field indicates the number ofsuper-frames ahead where the configuration will change. The nextsuper-frame with changes in the configuration is indicated by the valuesignaled within this field. If this field is set to the value ‘0000’, itmeans that no scheduled change is foreseen: e.g., value ‘1’ indicatesthat there is a change in the next super-frame.

FIC_CHANGE_COUNTER: This 4-bit field indicates the number ofsuper-frames ahead where the configuration (i.e., the contents of theFIC) will change. The next super-frame with changes in the configurationis indicated by the value signaled within this field. If this field isset to the value ‘0000’, it means that no scheduled change is foreseen:e.g. value ‘0001’ indicates that there is a change in the nextsuper-frame.

RESERVED: This 16-bit field is reserved for future use.

The following fields appear in the loop over NUM_DP, which describe theparameters associated with the DP carried in the current frame.

DP_ID: This 6-bit field indicates uniquely the DP within a PHY profile.

DP_START: This 15-bit (or 13-bit) field indicates the start position ofthe first of the DPs using the DPU addressing scheme. The DP_START fieldhas differing length according to the PHY profile and FFT size as shownin the below table 27.

TABLE 27 DP_START field size PHY profile 64K 16K Base 13 bit 15 bitHandheld — 13 bit Advanced 13 bit 15 bit

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks inthe current TI group for the current DP. The value of DP_NUM_BLOCKranges from 0 to 1023.

RESERVED: This 8-bit field is reserved for future use.

The following fields indicate the FIC parameters associated with theEAC.

EAC_FLAG: This 1-bit field indicates the existence of the EAC in thecurrent frame. This bit is the same value as the EAC_FLAG in thepreamble.

EAS_WAKE_UP_VERSION_NUM: This 8-bit field indicates the version numberof a wake-up indication.

If the EAC_FLAG field is equal to ‘1’, the following 12 bits areallocated for EAC_LENGTH_BYTE field. If the EAC_FLAG field is equal to‘0’, the following 12 bits are allocated for EAC_COUNTER.

EAC_LENGTH_BYTE: This 12-bit field indicates the length, in byte, of theEAC.

EAC_COUNTER: This 12-bit field indicates the number of the frames beforethe frame where the EAC arrives.

The following field appears only if the AUX_FLAG field is equal to ‘1’:

AUX_PRIVATE_DYN: This 48-bit field is reserved for future use forsignaling auxiliary streams. The meaning of this field depends on thevalue of AUX_STREAM_TYPE in the configurable PLS2-STAT.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS2.

FIG. 15 illustrates a logical structure of a frame according to anembodiment of the present invention.

As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummycells are mapped into the active carriers of the OFDM symbols in theframe. The PLS1 and PLS2 are first mapped into one or more FSS(s). Afterthat, EAC cells, if any, are mapped immediately following the PLS field,followed next by FIC cells, if any. The DPs are mapped next after thePLS or EAC, FIC, if any. Type 1 DPs follows first, and Type 2 DPs next.The details of a type of the DP will be described later. In some case,DPs may carry some special data for EAS or service signaling data. Theauxiliary stream or streams, if any, follow the DPs, which in turn arefollowed by dummy cells. Mapping them all together in the abovementioned order, i.e. PLS, EAC, FIC, DPs, auxiliary streams and dummydata cells exactly fill the cell capacity in the frame.

FIG. 16 illustrates PLS mapping according to an embodiment of thepresent invention.

PLS cells are mapped to the active carriers of FSS(s). Depending on thenumber of cells occupied by PLS, one or more symbols are designated asFSS(s), and the number of FSS(s) NFSS is signaled by NUM_FSS in PLS1.The FSS is a special symbol for carrying PLS cells. Since robustness andlatency are critical issues in the PLS, the FSS(s) has higher density ofpilots allowing fast synchronization and frequency-only interpolationwithin the FSS.

PLS cells are mapped to active carriers of the NFSS FSS(s) in a top-downmanner as shown in an example in FIG. 16. The PLS1 cells are mappedfirst from the first cell of the first FSS in an increasing order of thecell index. The PLS2 cells follow immediately after the last cell of thePLS1 and mapping continues downward until the last cell index of thefirst FSS. If the total number of required PLS cells exceeds the numberof active carriers of one FSS, mapping proceeds to the next FSS andcontinues in exactly the same manner as the first FSS.

After PLS mapping is completed, DPs are carried next. If EAC, FIC orboth are present in the current frame, they are placed between PLS and“normal” DPs.

FIG. 17 illustrates EAC mapping according to an embodiment of thepresent invention.

EAC is a dedicated channel for carrying EAS messages and links to theDPs for EAS. EAS support is provided but EAC itself may or may not bepresent in every frame. EAC, if any, is mapped immediately after thePLS2 cells. EAC is not preceded by any of the FIC, DPs, auxiliarystreams or dummy cells other than the PLS cells. The procedure ofmapping the EAC cells is exactly the same as that of the PLS.

The EAC cells are mapped from the next cell of the PLS2 in increasingorder of the cell index as shown in the example in FIG. 17. Depending onthe EAS message size, EAC cells may occupy a few symbols, as shown inFIG. 17.

EAC cells follow immediately after the last cell of the PLS2, andmapping continues downward until the last cell index of the last FSS. Ifthe total number of required EAC cells exceeds the number of remainingactive carriers of the last FSS mapping proceeds to the next symbol andcontinues in exactly the same manner as FSS(s). The next symbol formapping in this case is the normal data symbol, which has more activecarriers than a FSS.

After EAC mapping is completed, the FIC is carried next, if any exists.If FIC is not transmitted (as signaled in the PLS2 field), DPs followimmediately after the last cell of the EAC.

FIG. 18 illustrates FIC mapping according to an embodiment of thepresent invention.

shows an example mapping of FIC cell without EAC and (b) shows anexample mapping of FIC cell with EAC.

FIC is a dedicated channel for carrying cross-layer information toenable fast service acquisition and channel scanning. This informationprimarily includes channel binding information between DPs and theservices of each broadcaster. For fast scan, a receiver can decode FICand obtain information such as broadcaster ID, number of services, andBASE_DP_ID. For fast service acquisition, in addition to FIC, base DPcan be decoded using BASE_DP_ID. Other than the content it carries, abase DP is encoded and mapped to a frame in exactly the same way as anormal DP. Therefore, no additional description is required for a baseDP. The FIC data is generated and consumed in the Management Layer. Thecontent of FIC data is as described in the Management Layerspecification.

The FIC data is optional and the use of FIC is signaled by the FIC_FLAGparameter in the static part of the PLS2. If FIC is used, FIC_FLAG isset to ‘1’ and the signaling field for FIC is defined in the static partof PLS2. Signaled in this field are FIC_VERSION, and FIC_LENGTH_BYTE.FIC uses the same modulation, coding and time interleaving parameters asPLS2. FIC shares the same signaling parameters such as PLS2_MOD andPLS2_FEC. FIC data, if any, is mapped immediately after PLS2 or EAC ifany. FIC is not preceded by any normal DPs, auxiliary streams or dummycells. The method of mapping FIC cells is exactly the same as that ofEAC which is again the same as PLS.

Without EAC after PLS, FIC cells are mapped from the next cell of thePLS2 in an increasing order of the cell index as shown in an example in(a). Depending on the FIC data size, FIC cells may be mapped over a fewsymbols, as shown in (b).

FIC cells follow immediately after the last cell of the PLS2, andmapping continues downward until the last cell index of the last FSS. Ifthe total number of required FIC cells exceeds the number of remainingactive carriers of the last FSS, mapping proceeds to the next symbol andcontinues in exactly the same manner as FSS(s). The next symbol formapping in this case is the normal data symbol which has more activecarriers than a FSS.

If EAS messages are transmitted in the current frame, EAC precedes FIC,and FIC cells are mapped from the next cell of the EAC in an increasingorder of the cell index as shown in (b).

After FIC mapping is completed, one or more DPs are mapped, followed byauxiliary streams, if any, and dummy cells.

FIG. 19 illustrates an FEC structure according to an embodiment of thepresent invention.

FIG. 19 illustrates an FEC structure according to an embodiment of thepresent invention before bit interleaving. As above mentioned, Data FECencoder may perform the FEC encoding on the input BBF to generateFECBLOCK procedure using outer coding (BCH), and inner coding (LDPC).The illustrated FEC structure corresponds to the FECBLOCK. Also, theFECBLOCK and the FEC structure have same value corresponding to a lengthof LDPC codeword.

The BCH encoding is applied to each BBF (Kbch bits), and then LDPCencoding is applied to BCH-encoded BBF (Kldpc bits=Nbch bits) asillustrated in FIG. 22.

The value of Nldpc is either 64800 bits (long FECBLOCK) or 16200 bits(short FECBLOCK).

The below table 28 and table 29 show FEC encoding parameters for a longFECBLOCK and a short FECBLOCK, respectively.

TABLE 28 BCH error LDPC correction N_(bch) − Rate N_(ldpc) K_(ldpc)K_(bch) capability K_(bch) 5/15 64800 21600 21408 12 192 6/15 2592025728 7/15 30240 30048 8/15 34560 34368 9/15 38880 38688 10/15  4320043008 11/15  47520 47328 12/15  51840 51648 13/15  56160 55968

TABLE 29 BCH error LDPC correction N_(bch) − Rate N_(ldpc) K_(ldpc)K_(bch) capability K_(bch) 5/15 16200 5400 5232 12 168 6/15 6480 63127/15 7560 7392 8/15 8640 8472 9/15 9720 9552 10/15  10800 10632 11/15 11880 11712 12/15  12960 12792 13/15  14040 13872

The details of operations of the BCH encoding and LDPC encoding are asfollows:

A 12-error correcting BCH code is used for outer encoding of the BBF.The BCH generator polynomial for short FECBLOCK and long FECBLOCK areobtained by multiplying together all polynomials.

LDPC code is used to encode the output of the outer BCH encoding. Togenerate a completed Bldpc (FECBLOCK), Pldpc (parity bits) is encodedsystematically from each Ildpc (BCH-encoded BBF), and appended to Ildpc.The completed Bldpc (FECBLOCK) are expressed as following equation.

B _(ldpc)=[I _(ldpc) P _(ldpc)]=[i ₀ ,i ₁ , . . . ,i _(K) _(lpdc) ⁻¹ ,p₀ ,p ₁ , . . . ,p _(N) _(lpdc) _(−K) _(lpdc) ⁻¹]  [Equation 2]

The parameters for long FECBLOCK and short FECBLOCK are given in theabove table 28 and 29, respectively.

The detailed procedure to calculate Nldpc−Kldpc parity bits for longFECBLOCK, is as follows:

1) Initialize the parity bits,

p ₀ =p ₁ =p ₂ = . . . =p _(N) _(ldpc) _(−L) _(ldpc) ⁻¹=0  [equation3]

2) Accumulate the first information bit−i0, at parity bit addressesspecified in the first row of an addresses of parity check matrix. Thedetails of addresses of parity check matrix will be described later. Forexample, for rate 13/15:

$\begin{matrix}\begin{matrix}{p_{983} = {p_{983} \oplus i_{0}}} & {p_{2815} = {p_{2815} \oplus i_{0}}} \\{p_{4837} = {p_{4837} \oplus i_{0}}} & {p_{4989} = {p_{4989} \oplus i_{0}}} \\{p_{6138} = {p_{6138} \oplus i_{0}}} & {p_{6458} = {p_{6458} \oplus i_{0}}} \\{p_{6921} = {p_{6921} \oplus i_{0}}} & {p_{6974} = {p_{6974} \oplus i_{0}}} \\{p_{7572} = {p_{7572} \oplus i_{0}}} & {p_{8260} = {p_{8260} \oplus i_{0}}} \\{p_{8496} = {p_{8496} \oplus i_{0}}} & \;\end{matrix} & \left\lbrack {{Equation}\mspace{14mu} 4} \right\rbrack\end{matrix}$

3) For the next 359 information bits, is, s=1, 2, . . . , 359 accumulateis at parity bit addresses using following equation.

{x+(s mod 360)×

_(ldpc)}mod(N _(ldpc) −K _(ldpc))  [Equation 5]

where x denotes the address of the parity bit accumulator correspondingto the first bit i0, and Qldpc is a code rate dependent constantspecified in the addresses of parity check matrix. Continuing with theexample, Qldpc=24 for rate 13/15, so for information bit i1, thefollowing operations are performed:

$\begin{matrix}\begin{matrix}{p_{1007} = {p_{1007} \oplus i_{1}}} & {p_{2839} = {p_{2839} \oplus i_{1}}} \\{p_{4861} = {p_{4861} \oplus i_{1}}} & {p_{5013} = {p_{5013} \oplus i_{1}}} \\{p_{6162} = {p_{6162} \oplus i_{1}}} & {p_{6482} = {p_{6482} \oplus i_{1}}} \\{p_{6945} = {p_{6945} \oplus i_{1}}} & {p_{6998} = {p_{6998} \oplus i_{1}}} \\{p_{7596} = {p_{7596} \oplus i_{1}}} & {p_{8284} = {p_{8284} \oplus i_{1}}} \\{p_{8520} = {p_{8520} \oplus i_{1}}} & \;\end{matrix} & \left\lbrack {{Equation}\mspace{14mu} 6} \right\rbrack\end{matrix}$

4) For the 361st information bit i360, the addresses of the parity bitaccumulators are given in the second row of the addresses of paritycheck matrix. In a similar manner the addresses of the parity bitaccumulators for the following 359 information bits is, s=361, 362, . .. , 719 are obtained using the equation 6, where x denotes the addressof the parity bit accumulator corresponding to the information bit i360,i.e., the entries in the second row of the addresses of parity checkmatrix.

5) In a similar manner, for every group of 360 new information bits, anew row from addresses of parity check matrixes used to find theaddresses of the parity bit accumulators.

After all of the information bits are exhausted, the final parity bitsare obtained as follows:

6) Sequentially perform the following operations starting with i=1.

p _(i) =p _(i) ⊕p _(i−1) ,i=1,2, . . . ,N _(ldpc) −K_(ldpc)−1  [Equation 7]

where final content of pi, i=0, 1, . . . Nldpc−Kldpc−1 is equal to theparity bit pi.

TABLE 30 Code Rate Q_(ldpc) 5/15 120 6/15 108 7/15 96 8/15 84 9/15 7210/15  60 11/15  48 12/15  36 13/15  24

This LDPC encoding procedure for a short FECBLOCK is in accordance withthe LDPC encoding procedure for the long FECBLOCK, except replacing thetable 30 with table 31, and replacing the addresses of parity checkmatrix for the long FECBLOCK with the addresses of parity check matrixfor the short FECBLOCK.

TABLE 31 Code Rate Q_(ldpc) 5/15 30 6/15 27 7/15 24 8/15 21 9/15 1810/15  15 11/15  12 12/15  9 13/15  6

FIG. 20 illustrates a time interleaving according to an embodiment ofthe present invention.

(a) to (c) show examples of TI mode.

The time interleaver operates at the DP level. The parameters of timeinterleaving (TI) may be set differently for each DP.

The following parameters, which appear in part of the PLS2-STAT data,configure the TI:

DP_TI_TYPE (allowed values: 0 or 1): Represents the TI mode; ‘0’indicates the mode with multiple TI blocks (more than one TI block) perTI group. In this case, one TI group is directly mapped to one frame (nointer-frame interleaving). ‘1’ indicates the mode with only one TI blockper TI group. In this case, the TI block may be spread over more thanone frame (inter-frame interleaving).

DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TIblocks NTI per TI group. For DP_TI_TYPE=‘1’, this parameter is thenumber of frames PI spread from one TI group.

DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): Represents the maximumnumber of XFECBLOCKs per TI group.

DP_FRAME_INTERVAL (allowed values: 1, 2, 4, 8): Represents the number ofthe frames HUMP between two successive frames carrying the same DP of agiven PHY profile.

DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not usedfor a DP, this parameter is set to ‘1’. It is set to ‘0’ if timeinterleaving is used.

Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is usedto represent the number of XFECBLOCKs carried by one TI group of the DP.

When time interleaving is not used for a DP, the following TI group,time interleaving operation, and TI mode are not considered. However,the Delay Compensation block for the dynamic configuration informationfrom the scheduler will still be required. In each DP, the XFECBLOCKsreceived from the SSD/MIMO encoding are grouped into TI groups. That is,each TI group is a set of an integer number of XFECBLOCKs and willcontain a dynamically variable number of XFECBLOCKs. The number ofXFECBLOCKs in the TI group of index n is denoted by NxBLOCK_Group(n) andis signaled as DP_NUM_BLOCK in the PLS2-DYN data. Note thatNxBLOCK_Group(n) may vary from the minimum value of 0 to the maximumvalue NxBLOCK_Group_MAX (corresponding to DP_NUM_BLOCK_MAX) of which thelargest value is 1023.

Each TI group is either mapped directly onto one frame or spread over PIframes. Each TI group is also divided into more than one TI blocks(NTI), where each TI block corresponds to one usage of time interleavermemory. The TI blocks within the TI group may contain slightly differentnumbers of XFECBLOCKs. If the TI group is divided into multiple TIblocks, it is directly mapped to only one frame. There are three optionsfor time interleaving (except the extra option of skipping the timeinterleaving) as shown in the below table 32.

TABLE 32 Modes Descriptions Option-1 Each TI group contains one TI blockand is mapped directly to one frame as shown in (a). This option issignaled in the PLS2-STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH =‘1’(N_(TI) = 1). Option-2 Each TI group contains one TI block and ismapped to more than one frame. (b) shows an example, where one TI groupis mapped to two frames, i.e., DP_TI_LENGTH = ‘2’ (P_(I) = 2) andDP_FRAME_INTERVAL (I_(JUMP) = 2). This provides greater time diversityfor low data-rate services. This option is signaled in the PLS2-STAT byDP_TI_TYPE = ‘1’. Option-3 Each TI group is divided into multiple TIblocks and is mapped directly to one frame as shown in (c). Each TIblock may use full TI memory, so as to provide the maximum bit-rate fora DP. This option is signaled in the PLS2-STAT signaling by DP_TI_TYPE =‘0’ and DP_TI_LENGTH = N_(TI), while P_(I) = 1.

Typically, the time interleaver will also act as a buffer for DP dataprior to the process of frame building. This is achieved by means of twomemory banks for each DP. The first TI-block is written to the firstbank. The second TI-block is written to the second bank while the firstbank is being read from and so on.

The TI is a twisted row-column block interleaver. For the sth TI blockof the nth TI group, the number of rows N_(r) of a TI memory is equal tothe number of cells N_(cells), i.e., N_(r)=N_(cells) while the number ofcolumns N_(c) is equal to the number N_(xBLOCK) _(_) _(TI)(n,s).

FIG. 21 illustrates the basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention.

FIG. 21(a) shows a writing operation in the time interleaver and FIG.21(b) shows a reading operation in the time interleaver The firstXFECBLOCK is written column-wise into the first column of the TI memory,and the second XFECBLOCK is written into the next column, and so on asshown in (a). Then, in the interleaving array, cells are read outdiagonal-wise. During diagonal-wise reading from the first row(rightwards along the row beginning with the left-most column) to thelast row, N_(r) cells are read out as shown in (b). In detail, assumingz_(n,s,i) (i=0, . . . , N_(r)N_(c)) as the TI memory cell position to beread sequentially, the reading process in such an interleaving array isperformed by calculating the row index R_(n,s,i), the column indexC_(n,s,i), and the associated twisting parameter T_(n,s,i) as followsequation.

$\begin{matrix}{{GENERATE}\left\{ {{R_{n,s,i} = {{mod}\left( {i,N_{r}} \right)}},{T_{n,s,i} = {{mod}\left( {{S_{shift} \times R_{n,s,i}},N_{c}} \right)}},{C_{n,s,i} = {{mod}\left( {{T_{n,s,i} + \left\lfloor \frac{i}{N_{r}} \right\rfloor},N_{c}} \right)}}} \right\}} & \left\lbrack {{Equation}\mspace{14mu} 8} \right\rbrack\end{matrix}$

where S_(shift) is a common shift value for the diagonal-wise readingprocess regardless of N_(xBLOCK) _(_) _(TI)(n,s), and it is determinedby N_(xBLOCK) _(_) _(TI) _(_) _(MAX) given in the PLS2-STAT as followsequation.

$\begin{matrix}{{for}\left\{ {\begin{matrix}{\begin{matrix}{N_{{xBLOCK}\; \_ \; {TI}\; {\_ {MAX}}}^{\prime} =} \\{N_{{xBLOCK}\; \_ \; {TI}\; {\_ {MAX}}} + 1}\end{matrix},} & {{{if}\mspace{14mu} N_{{xBLOCK}\; \_ \; {TI}\; {\_ {MAX}}}{mod}\; 2} = 0} \\{\begin{matrix}{N_{{xBLOCK}\; \_ \; {TI}\; {\_ {MAX}}}^{\prime} =} \\N_{{xBLOCK}\; \_ \; {TI}\; {\_ {MAX}}}\end{matrix},} & {{{if}\mspace{14mu} N_{{xBLOCK}\; \_ \; {TI}\; {\_ {MAX}}}{mod}\; 2} = 1}\end{matrix},{S_{shift} = \frac{N_{{xBLOCK}\; \_ \; {TI}\; {\_ {MAX}}}^{\prime} - 1}{2}}} \right.} & \left\lbrack {{Equation}\mspace{14mu} 9} \right\rbrack\end{matrix}$

As a result, the cell positions to be read are calculated by acoordinate as z_(n,s,i)=N_(r)C_(n,s,i)+R_(n,s,i).

FIG. 22 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention.

More specifically, FIG. 22 illustrates the interleaving array in the TImemory for each TI group, including virtual XFECBLOCKs when N_(xBLOCK)_(_) _(TI)(0,0)=3, N_(xBLOCK) _(_) _(TI)(1,0)=6, N_(xBLOCK) _(_)_(TI)(2,0)=5.

The variable number N_(xBLOCK) _(_) _(TI)(n,s)=N_(r) will be less thanor equal to N_(xBLOCK) _(_) _(TI) _(_) _(MAX)′. Thus, in order toachieve a single-memory deinterleaving at the receiver side, regardlessof N_(xBLOCK) _(_) _(TI)(n,s), the interleaving array for use in atwisted row-column block interleaver is set to the size ofN_(r)×N_(c)=N_(cells)×N_(xBLOCK) _(_) _(TI) _(_) _(MAX)′ by insertingthe virtual XFECBLOCKs into the TI memory and the reading process isaccomplished as follow equation.

$\begin{matrix}{{{p = 0};}{{{for}\mspace{14mu} i} = {{{0\text{;}i} < {N_{cells}N_{{{xBLOCK}\_ {TI}}{\_ {MAX}}}^{\prime}\text{;}i}} = {i + 1}}}\left\{ {{{GENERATE}\left( {R_{n,s,i}\text{,}C_{n,s,i}} \right)};{V_{i} = {{{N_{r}C_{n,s,j}} + {R_{n,s,j}{if}\mspace{11mu} V_{i}}} < {N_{cells}{N_{{xBLOCK}\_ {TI}}\left( {n\text{,}s} \right)}\left\{ {{Z_{n,s,p} = V_{i}};{p = {p + 1}};} \right\}}}}} \right\}} & \left\lbrack {{Equation}\mspace{14mu} 10} \right\rbrack\end{matrix}$

The number of TI groups is set to 3. The option of time interleaver issignaled in the PLS2-STAT data by DP_TI_TYPE=‘0’, DP_FRAME_INTERVAL=‘1’,and DP_TI_LENGTH=‘1’, i.e., NTI=1, IJUMP=1, and PI=1. The number ofXFECBLOCKs, each of which has Ncells=30 cells, per TI group is signaledin the PLS2-DYN data by NxBLOCK TI(0,0)=3, NxBLOCK TI(1,0)=6, andNxBLOCK TI(2,0)=5, respectively. The maximum number of XFECBLOCK issignaled in the PLS2-STAT data by NxBLOCK_Group_MAX, which leads to└N_(xBLOCK) _(_) _(Group) _(_) _(MAX)/N_(TI)┘=N_(xBLOCK) _(_) _(TI) _(_)_(MAX)=6.

FIG. 23 illustrates a diagonal-wise reading pattern of a twistedrow-column block interleaver according to an embodiment of the presentinvention.

More specifically FIG. 23 shows a diagonal-wise reading pattern fromeach interleaving array with parameters of N_(xBLOCK) _(_) _(TI) _(_)_(MAX)′=7 and Sshift=(7−1)/2=3. Note that in the reading process shownas pseudocode above, if V_(i)≥N_(cells)N_(xBLOCK) _(_) _(TI)(n,s), thevalue of Vi is skipped and the next calculated value of Vi is used.

FIG. 24 illustrates interleaved XFECBLOCKs from each interleaving arrayaccording to an embodiment of the present invention.

FIG. 24 illustrates the interleaved XFECBLOCKs from each interleavingarray with parameters of N_(xBLOCK) _(_) _(TI) _(_) _(MAX)′=7 andSshift=₃.

FIG. 25 is a block diagram illustrating a main physical device and acompanion physical device according to an embodiment of the presentinvention.

The embodiment of the present invention can provide a service guide in aterrestrial broadcast environment or a mobile broadcast environment. Inaddition, the embodiment of the present invention can provide a serviceguide regarding services available in the next generation hybridbroadcast environment based on interaction between a terrestrialbroadcast network and the Internet.

The embodiment of the present invention can inform users of not onlyvarious services available in the next generation hybrid broadcastsystem, but also constituent content of the services and/or componentelements of the services. As a result, the user can easily confirm,select, and view the corresponding service, resulting in increased userconvenience.

The embodiment of the present invention may construct a single service,various constituent content of the service, and/or component elements ofthe service, and may make a cross reference to each other. As a result,the broadcast receiver can easily construct and provide thecorresponding service, and can allow the user to easily recognize thecorresponding service.

The embodiments of the present invention can extend the referencestructure for linking one service to various content and/or componentelements of the service, and can allow the broadcast receiver and/or theuser to reduce the amount of resources and/or consumption time needed tosearch for content and/or component elements of the single service.

FIG. 25 is a block diagram illustrating a main physical device and acompanion physical device according to an embodiment of the presentinvention.

The main physical device (L25010) according to an embodiment of thepresent invention is one of devices for interactive services, and mayindicate a target device to be controlled by the companion physicaldevice (L25020). The main physical device may be referred to as a maindevice, a main reception device, a main display, a main screen, or thelike.

The main physical device (L25010) according to one embodiment of thepresent invention may include a broadcast interface (L25030), a networkinterface (L25040), a memory unit (L25050), a control unit (L25060), adisplay unit (L25070), a multimedia module (L25080), a storage unit(L25090), a power-supply unit (L25100), and/or a user input interface(L25110).

The broadcast interface (L25030) may indicate a physical device locatedbetween the broadcaster and the device, such that the broadcastinterface (L25030) acting as the physical device can transmit variousmessages (such as the AV stream, service guide, and notificationmessages) and/or data. The broadcast interface (L25030) may receivebroadcast signals, signaling information, data, etc. from thebroadcaster.

The network interface (L25040) may indicate a physical device locatedbetween various devices (e.g., the main physical device and thecompanion physical device), such that the network interface (L25040) cantransmit various messages (e.g., commands, requests, actions, responsemessages, etc.), and can perform advertising and/or data transmission.The network interface may receive broadcast services, broadcast content,signaling information, applications, data, etc. from the Internetservice provider.

The memory unit (L25050) may be an optional or selective deviceimplemented in various types of devices, and may indicate a volatilephysical device capable of temporarily storing various types of data.

The control unit (L25060) may be configured to control the entireoperation of the source device and/or the sink device, and may beimplemented by software or hardware. In this case, the source device mayindicate a device configured to transmit messages and/or data. The sinkdevice may indicate a device configured to receive messages and/or data.Therefore, the main physical device and the companion physical deviceaccording to the embodiment of the present invention may correspond tothe source device or the sink device.

The display unit (L25070) may display data received through the networkinterface or data stored in the storage unit on the screen. In thiscase, the display unit may be controlled by the control unit.

The multimedia module (L25080) may reproduce various types ofmultimedia. The multimedia module may be contained in the control unit,and may be located independently of the control unit.

The storage unit (L25090) may indicate a non-volatile physical devicecapable of storing various types of data therein. For example, the SCcard may correspond to the storage unit.

The power-supply unit (L25100) may receive the external power-supplyvoltage and/or the internal power-supply voltage under control of thecontrol unit, such that the power-supply unit (L25100) can provide apower-supply voltage needed to operate other constituent elements.

The user input interface (L25110) may indicate a device capable ofreceiving input signals or commands from the user.

The companion physical device (L25020) according to the embodiment ofthe present invention may be one of devices needed for interactiveservices, and may indicate a device configured to control the maindevice. Generally, the companion physical device may directly receiveinput signals from the user. The companion physical device may bereferred to as a companion device, a second device, an additionaldevice, an auxiliary device, a companion reception device, a companionreceiver, a companion display, a second screen, or the like.

The physical device (L25020) according to the embodiment of the presentinvention may include a network interface, a memory unit, a controlunit, a display unit, a multimedia module, a storage unit, apower-supply unit, and/or a user input interface.

From among all the constituent elements of the companion physical deviceaccording to the embodiment, some constituent elements having the samenames as those of the main device may have the same functions as thoseof the constituent elements of the above-mentioned main device.

FIG. 26 is a block diagram illustrating a protocol stack configured tosupport a hybrid broadcast service according to an embodiment of thepresent invention.

A physical layer may receive terrestrial broadcast signals, and mayproperly convert (or transform) the received terrestrial broadcastsignals.

IP (Internet Protocol) Encapsulation may acquire an IP datagram usinginformation acquired from the physical layer. In addition, the IPencapsulation may convert (or transform) the acquired IP datagram into aspecific frame (e.g., RS Frame, GSE, etc.).

MPEG2 TS Encapsulation may acquire the MPEG2 TS using informationacquired from the physical layer. In addition, the MPEG2 TSEncapsulation may convert the acquired MPEG2 TS datagram into a specificframe (e.g., RS Frame, GSE, etc.).

A Fast Information Channel (FIC) may transmit specific information(e.g., mapping information between the service ID and the frame) so asto access the service and/or content.

Signaling may include signaling information to support a hybridbroadcast service according to an embodiment of the present invention.This signaling information may include signaling information to supportefficient acquisition of the services and/or content. This signalinginformation may be denoted in binary and/or XML format, and may betransmitted through the terrestrial broadcast network and/or thebroadband network.

Real time A/V (Audio/Video) content and data may be represented by ISOBase Media File Format (ISOBMFF) or the like, and may be transmitted inreal time through the terrestrial broadcast network and/or the broadbandnetwork. Non-real time content may be transmitted on the basis ofIP/UDP/FLUTE. Real-time broadcast A/V (Audio/Video) content, data and/orsignaling information may be transmitted in real time through theInternet. In this case, the real-time broadcast A/V (Audio/Video)content, data and/or signaling information may be transmitted by arequest message. Alternatively, the real-time broadcast A/V(Audio/Video) content, data and/or signaling information may also betransmitted through real-time streaming.

The embodiment of the present invention may combine data through theabove-mentioned protocol stack, and may also provide various enhancedservices, for example, an interactive service, a second screen service,etc.

FIG. 27 is a conceptual diagram illustrating an XML schema of a ServiceType element according to an embodiment of the present invention.

Prior to describing FIG. 27, definition and structure of the serviceguide, the service fragment, and the ServiceType element according tothe embodiment will be described as follows.

The service guide may indicate a broadcast distribution channel overwhich Service Guide Delivery Descriptors carried within announcementsessions, can be delivered to the terminal.

Service Guide may enable the service and content providers to describethe services and content they make available, or offer for subscriptionor purchase, as Mobile Broadcast services either over Broadcast Channelor over Interaction Channel. It may also enable the way to describe howto access the services. From the user perspective the Service Guide canbe seen as an entry point to discover the currently available orscheduled services and content and to filter those based on theirpreferences. Furthermore, the Service Guide may provide the entry pointto interactive services.

The Service Guide may include data model that models the services,schedules, content, related purchase and provisioning data, access andinteractivity data and so on in terms of Service Guide fragments.

An embodiment of the invention may provide methods for initial discoveryof Service Guide and the declaration of Service Guide fragments throughService Guide Delivery Descriptors that are sent over Service GuideAnnouncement Channel. An embodiment of the invention may providedelivery methods specified for Service Guide fragment delivery overService Guide Delivery Channel, both over the Broadcast Channel as wellas over the Interactive Channel. To manage the Service Guide data, anembodiment of the invention may provide update and management methods.An embodiment of the invention may provide the relevant backendinterfaces for Service Guide.

The ‘Service’ fragment may describe the content items which comprise abroadcast service, at an aggregate level.

Depending on the type of the service, it may have interactive part(s),broadcastonly part(s), or both.

The service fragment may include components not directly related to thecontent but to the functionality of the service such as purchasing orsubscription information.

In accordance with one embodiment of the present invention, as the partof the Service Guide, the ‘Service’ fragment may form a central hubreferenced by the other fragments.

Together with the associated fragments, the terminal may determine thedetails associated with the service at any point of time. These detailsmay be summarized into a user-friendly display, for example, of what,how and when the associated content may be consumed and at what cost.

A service may represent a bundle of content items, which forms a logicalgroup to the end-user. An example would be a TV channel, composed ofseveral TV shows. A ‘Service’ fragment contains the metadata describingthe Mobile Broadcast service.

ServiceType element may indicate the type of a service written in thecorresponding service fragment. The mixed service types may be indicatedby the presence of multiple instances of ServiceType. This element maybe processed by the terminal strictly for rendering to the user forexample as a textual indicator, an icon, or graphic representation forthe service.

The embodiments of the present invention provide a method forrepresenting a service type used in a hybrid broadcast system. Inaddition, according to the embodiment, the range of ServiceType valuesto be shown in the hybrid broadcast system may be allocated to theServiceTypeRangeType value.

The values allocated to the Service Type fragment according to theembodiment are as follows. If the Service Type value is set to zero ‘0’,this means “Unspecified”. If the Service Type value is set to 1, thismeans that the corresponding service is Basic TV. If the Service Typevalue is set to 2, this means that the corresponding service is BasicRadio. If the Service Type value is set to 3, this means that thecorresponding service is a Rights Issuer Service. If the Service Typevalue is set to 4, this means ‘Cachecast’. If the Service Type value isset to 5, this means ‘File download services’. If the Service Type valueis set to 6, this means ‘Software management services’. If the ServiceType value is set to 7, this means ‘Notification’. If the Service Typevalue is set to 8, this means ‘Service Guide’. If the Service Type valueis set to 9, this means ‘Terminal Provisioning services’. If the ServiceType value is set to 10, this means ‘Auxiliary Data’. If the ServiceType value is set to 11, this means ‘Streaming on demand’. If theService Type value is set to 12, this means ‘File download on demand’.If the Service Type value is set to 14, this means ‘Linear service’. Ifthe Service Type value is set to 15, this means ‘AppBased service’. Ifthe Service Type value is set to 16, this means ‘Companion Screenservice’. The remaining values other than the above-mentioned values mayalso be used to represent other services other than the above-mentionedservices.

Referring to FIG. 27, the ServiceType element according to theembodiment may have the value of ServiceTypeRangeType.ServiceTypeRangeType may include ServiceTypeLRType,ServiceTypeOtherEnablersRangeType, and/orServiceTypeProprietaryRangeType. In this case, ServiceTypeLRType mayhave a minimum value of 0, and may have any one of 13, 14, 15, 16 orhigher as a maximum value.

FIG. 28 illustrates an XML schema regarding a specific service having aservice type value of 14, and an exemplary display image thereofaccording to an embodiment of the present invention.

Referring to FIG. 28, the Service fragment may be entitled ‘Home andShopping’, and may have the ServiceType value of 14. (L28010).

The ServiceType value of 14 may represent a Linear Service. In thiscase, the reception apparatus according to the embodiment can recognizethat scheduling information of the service guide is contained in thescreen when the selected service type is set to Linear Service(value=14). In addition, the embodiment of the present invention canprovide the user with broadcast program schedule information bycombining the corresponding service with schedule information. (L28020).In addition, if the service type is signaled in the service fragment,the receiver has only to combine the above-mentioned scheduleinformation with the service including time information. Therefore, theembodiment of the present invention can improve throughput orperformance of the receiver.

FIG. 29 illustrates an XML schema regarding a specific service havingservice type values 14 and 15, and an exemplary display image thereofaccording to an embodiment of the present invention.

Service Fragment according to the embodiment may be entitled ‘MBC’, andmay have the Service Type values 14 and 15. (L29010).

The ServiceType value of 15 may indicate ‘AppBased service’. If theAppBased service type is signaled in the service fragment, the receptionapparatus according to the embodiment can recognize that the AppBasedService is contained in the corresponding service. (L29020). Therefore,although the embodiment has obtained only the Service fragment, it mayinform the user that the associated App can be executed through theServiceType in L29030. As shown in FIG. 29, since the service entitled‘MBC’ also includes the ServiceType value 14, the effects of the presentinvention may also be achieved when the corresponding service is LinearService (value=14), and associated description has already beendisclosed above.

FIG. 30 illustrates an XML schema regarding a specific service havingservice type values 14 and 16, and an exemplary display image thereofaccording to an embodiment of the present invention.

Referring to FIG. 30, the Service fragment may be entitled ‘MBCCompanion Screen’, and may have the ServiceType values (14, 16).(L30010).

The ServiceType value 16 may indicate a Companion Screen service. If theCompanion Screen service type is signaled in the service fragment, thereception apparatus according to the embodiment can recognize that theCompanion Screen service is contained in the corresponding service.(L30020). Therefore, although the embodiment has obtained only theService fragment, it may inform the user of the presence of servicessupplied from the Companion Screen. (L30030). As shown in FIG. 30, sincethe MBC Companion Screen service also includes the ServiceType value 14,the effects of the present invention may also be achieved when thecorresponding service is Linear Service (value=14), and associateddescription has already been disclosed above.

FIG. 31 illustrates an XML schema of a Component Fragment according toan embodiment of the present invention.

Referring to FIG. 31, the Component fragment according to one embodimentmay describe some parts of content to be referenced by the component, ormay describe some parts of the service to be referenced by thecomponent. (The ‘Component’ fragment describes a component that is apart of a service or a content that the component refers to).

The Component fragment according to the embodiment may include an ‘id’attribute, a version attribute, a validFrom attribute, a validToattribute, a ComponentType element, a ComponentData element, and/or aPrivateExt element.

The ‘id’ attribute may indicate an ID of the component fragment. Thisattribute value may be globally unique.

The version attribute may indicate version information of the componentfragment.

The validFrom attribute may indicate an initial time at which thecomponent fragment is valid.

The validTo attribute may denote the last time at which the componentfragment is valid.

The ComponentType element may indicate the type of content to bedescribed by the component fragment. If several types are mixed, theComponentType may indicate the type using one or more ComponentTypeelements.

The ComponentData element may indicate Component Content contained inthe component fragment. This element may indicate video, audio or CC(Closed Caption) data.

The PrivateExt element may indicate a container for proprietary orapplication-specified extension. (The PrivateExt element may serve as acontainer for proprietary or application specific extensions).

FIG. 32 illustrates an XML schema of a ComponentType element accordingto an embodiment of the present invention.

Referring to FIG. 32, the component may indicate all ComponentTypeinformation capable of being transmitted through hybrid broadcasting.For this purpose, the embodiment of the present invention may indicatethe range of type as an integer value.

In accordance with the embodiment, not all the components include data(ComponentData), such that the reception apparatus can first recognizethe type value of the component fragment, and then recognize informationregarding component data.

The relationship between subordinates and superiors of the components orthe subordinate relationship of the respective components willhereinafter be given.

In accordance with the embodiment, the ComponentRangeType indicating theComponentType element type may be set to zero as a minimum value, andmay be set to 13 as a maximum value.

As shown in FIG. 32, if the ComponentType element value is set to zero,this means ‘Unspecified’. If the ComponentType element value is set to1, this means a Continuous component. If the ComponentType element valueis set to 2, this means an Elementary component. If the ComponentTypeelement value is set to 3, this means a Composite component. If theComponentType element value is set to 4, this means a PickOne component.If the ComponentType element value is set to 5, this means a Complexcomponent. If the ComponentType element value is set to 6, this means aPresentable component. If the ComponentType element value is set to 7,this means an NRT File. If the ComponentType element value is set to 8,this means an NRT Content Item. If the ComponentType element value isset to 9, this means an Application. If the ComponentType element valueis set to 10, this means ‘ATSC3.0 Application’. If the ComponentTypeelement value is set to 11, this means an On Demand component. If theComponentType element value is set to 12, this means a NotificationStream. If the ComponentType element value is set to 13, this means anAppBased Enhancement. If the ComponentType element value is set to anyone of 14 to 25, this means ‘Reserved’.

The Continuous component may indicate a content component represented inone continuous stream. For example, the Continuous component maycorrespond to Audio, Video, or Closed Caption.

The Elementary component may indicate a Continuous componentcorresponding to single encoding. That is, the Elementary component mayindicate a Continuous component encoded by a separate encoder. Forexample, single encoding of the sound sequence, single encoding of thepicture sequence, or the single closed caption track may correspond tothe Elementary component.

The Composite component may indicate a content component constructingthe set of continuous components which have the same content type,represent the same scene, and can be combined to construct onepresentation. For example, the Composite component may be implemented asmusic, dialogue, and sound effect, which are to be mixed to providehigh-quality audio. In addition, a left-eye image and a right-eye imageto be combined to construct a three dimensional (3D) image may alsocorrespond to the composite component.

The PickOne component may indicate a content component constructing theset of continuous components capable of being selected to have the samecontent type, display the same scene, and construct one presentation.For example, the set of audio components encoded by bit rates differentfrom those of the same sound sequence, the set of video componentsencoded by bit rates different from those of the same picture sequence,or the set of general closed caption tracks and easy reader closedcaption tracks for the same dialogue may correspond to the PickOnecomponent.

The Complex component may indicate the Composite component or thePickOne component.

The Presentable component may denote the Continuous component displayedfor the user. This component may include the Elementary component orComplex component.

The NRT File may indicate a non-realtime transmission file.

The NRT Content Item may indicate the set of one or more NRT files to bepackage-consumed by users who will purchase the set of NRT files.

The Application may indicate the set of constituent documents of thecomplete enhanced or interactive service. The above-mentioned documentsmay include HTML, JavaScript, CSS, XML, and/or multimedia files. TheApplication may access other data instead of the part of theapplication. This Application may correspond to a special case of NRTContent Item.

The ATSC3.0 Application may indicate Application based on ATSC 3.0Application Runtime Environment Specification.

The On Demand component may indicate a content component transmitted ondemand.

The Notification Stream may indicate a stream capable of transmitting anotification message configured to synchronize actions of theapplication under Linear Time Base.

The AppBased Enhancement may include zero or more Notification Streamsto transmit synchronized notification of the actions, one or moreapplications, zero or more different NRT Content Items used by theapplication, and zero or more On Demand components managed by theapplication.

FIG. 33 illustrates an XML schema of a ComponentData element accordingto an embodiment of the present invention.

Referring to FIG. 33, the embodiment of the present invention may definethe ComponentData element as the schema so as to direct or guidecharacteristics of the actual Component Data.

The ComponentData element according to the embodiment may represent theComponent Data according to the combination or relationship betweenrespective types, when the ComponentType element value of theabove-mentioned component fragment is set to 2, 3, 4 or 6.

In accordance with the embodiment, each component may have theContentType attribute. The ContentType attribute may have Video, Audio,and/or CC (Closed Caption) values.

As can be seen from the schema of FIG. 33, the embodiment of the presentinvention can provide a method for describing the Component Dataaccording to each ContentType attribute. That is, the ComponentDataelement according to the embodiment may have the VideoComponent elementas a lower element, when the ContentType attribute value is denoted by‘Video’. If the ContentType attribute value is denoted by ‘Audio’, theAudioComponent element may be used as a lower element. If theContentType attribute value is denoted by CC, the CCComponent elementmay be used as a lower element. In addition, each Component Data may bedescribed (or written) in the lower element.

FIG. 34 illustrates an XML schema of a VideoComponent element and aVideoRole element according to an embodiment of the present invention.

The embodiment of the present invention can provide a method fordescribing a Video Component used in hybrid broadcasting.

The VideoComponent element according to the embodiment may include aVideoRole element, a TargetUserProfile element, and/or a TargetDeviceelement as lower elements. (L34010).

The VideoRole element may indicate the role of the corresponding VideoComponent. In accordance with the embodiment, the VideoRole element mayhave an integer value in consideration of future extensibility. Inaddition, this embodiment can provide the range of the above VideoRoleelement in such a manner that not only the role achieved when the VideoComponent is denoted by ‘presentable’, but also the other role achievedwhen the Video Component is denoted by ‘composite’ can be displayed.

The TargetUserProfile element and the TargetDevice element maycorrespond to the common element of all the presentable components.These elements may indicate attributes of the target.

If the VideoRole element according to the embodiment is denoted by 0,this means ‘Unspecified’. If the VideoRole element is denoted by 1, thismeans ‘Primary (default) video’. If the VideoRole element is denoted by2, this means ‘Alternative camera view’. If the VideoRole element isdenoted by 3, this means ‘Other alternative video component’. If theVideoRole element is denoted by 4, this means ‘Sign language (e.g., ASL)inset’. If the VideoRole element is denoted by 5, this means ‘Followsubject video’. If the VideoRole element is denoted by 6, this means‘Base layer for scalable video encoding’. If the VideoRole element isdenoted by 7, this means ‘Enhancement layer for scalable video encodingwith level’. If the VideoRole element is denoted by 8, this means ‘3Dvideo left view’. If the VideoRole element is denoted by 9, this means‘3D video right view’. If the VideoRole element is denoted by 10, thismeans ‘3D video depth information’. If the VideoRole element is denotedby 11, this means ‘Part of video array, <x,y> of <n,m>. If the VideoRoleelement is denoted by 12, this means ‘FollowSubject metadata’. If theVideoRole element is denoted by 13˜25, this means ‘Reserved’. If theVideoRole element is denoted by 0˜5, this means the role of PresentableVideo Component. If the VideoRole element is denoted by 6˜12, this meansthe role of Composite Video Component. If the VideoRole element isdenoted by 13˜255, this means the role of ‘Other Video Component’.(L34020)

FIG. 35 illustrates an XML schema of an AudioComponent element and anAudioRole element according to an embodiment of the present invention.

The embodiment of the present invention can provide a method fordescribing Audio Component used in hybrid broadcasting.

The AudioComponent element according to the embodiment may have theassociatedTo attribute and/or the NumberOfAudioChannels attribute. TheAudioComponent element may have the AudioRole element, theTargetUserProfile element, and/or the TargetDevice element as lowerelements. (L35010)

The associatedTo attribute may indicate whether the corresponding AudioComponent is associated with the Presentable Video Component. Thisattribute may have an id value of the component fragment.

The NumberOfAudioChannels attribute may indicate the number of AudioComponent channels.

The AudioRole element may indicate the role of the corresponding AudioComponent. In accordance with the embodiment, the AudioRole element mayhave an integer value in consideration of future extensibility.

The TargetUserProfile and the TargetDevice element may correspond to thecommon element of all the presentable components. These elements mayrepresent target attributes.

The AudioRole element according to the embodiment may have the values of0˜7. If the AudioRole element is set to zero ‘0’, this means‘Unspecified’. If the AudioRole element is set to 1, this means‘Complete main’. If the AudioRole element is set to 2, this means‘Music’. If the AudioRole element is set to 3, this means ‘Dialog’. Ifthe AudioRole element is set to 4, this means ‘Effects’. If theAudioRole element is set to 5, this means ‘Visually impaired’. If theAudioRole element is set to 6, this means ‘Hearing impaired’. If theAudioRole element is set to 7, this means ‘Commentary’. If the AudioRoleelement is set to the values of 8 to 255, this means ‘Reserved’.(L35020)

FIG. 36 illustrates an XML schema of a CCComponent element and a CCRoleelement according to an embodiment of the present invention.

Referring to FIG. 36, the embodiment can provide a method for describinga CC Component used in hybrid broadcasting.

The CCComponent element according to the embodiment may have anassociatedTo attribute, a CCRole element, a TargetUserProfile element,and/or a TargetDevice element as lower elements. (L36010)

The associatedTo attribute may indicate whether the corresponding CCComponent is associated with the Presentable Video Component. TheassociatedTo attribute may have an ‘id’ value of the component fragment.

The associatedTo attribute may indicate the role of the corresponding CCComponent. In accordance with the embodiment, the associatedTo attributemay have an integer value in consideration of the future extensibility.

The TargetUserProfile element and the TargetDevice element maycorrespond to the common element of all the presentable components. TheTargetUserProfile and TargetDevice elements may indicate targetattributes.

The CCRole element according to the embodiment may have the values of 0to 2. If the CCRole element is set to zero (0), this means‘unspecified’. If the CCRole element is set to 1, this means ‘normal’.If the CCRole element is set to 2, this means the easy reader. (L36020)

FIG. 37 illustrates an XML schema of component fragments regarding aComposite Video Component including one base layer and two enhancementlayers in scalable video coding according to an embodiment of thepresent invention.

In accordance with this embodiment, the component fragment (L37010)located at the top of FIG. 37 may have the ID value“bcast://lge.com/Component/1”, and may indicate that the correspondingcomponent is any of the Continuous and Composite components using theComponentType element.

The Component fragment (L37020) located to the left of FIG. 37 may have“bcast://lge.com/Component/2” as the ID value, and may indicate that thecorresponding component is any of the Continuous and Elementarycomponents using the ComponentType element. In addition, the Componentfragment (L37020) may indicate that the corresponding component relatesto the Video component using the ComponentData element, the ContentTypeattribute, the VideoComponent element, and the VideoRole element, andmay indicate that the corresponding element is a “Base Layer of SVC”component.

The Component fragment (L37030) located to the right of FIG. 37 may have“bcast://lge.com/Component/3” as the ID value, and may indicate that thecorresponding component is any of the Continuous and Elementarycomponents using the ComponentType element. In addition, the Componentfragment (L37030) may indicate that the corresponding component relatesto the Video component using the ComponentData element, the ContentTypeattribute, the VideoComponent element, and the VideoRole element, andmay indicate that the corresponding element is an “Enhancement Layer ofSVC” component.

FIG. 38 illustrates an XML schema of component fragments regarding aComposite Component including a 3D video left view and a 3D video rightview according to an embodiment of the present invention.

In accordance with the embodiment, the Component fragment (L38010)located to the top of FIG. 38 may have “bcast://lge.com/Component/1” asthe ID value, and may indicate that the corresponding component is anyof the Continuous and Composite components using the ComponentTypeelement.

The Component fragment (L38020) located to the left of FIG. 38 may have“bcast://lge.com/Component/2” as the ID value, and may indicate that thecorresponding component is any of the Continuous and PickOne componentsusing the ComponentType element. In addition, the Component fragment(L38020) may indicate that the corresponding component relates to theVideo component using the ComponentData element, the ContentTypeattribute, the VideoComponent element, and the VideoRole element, andmay indicate that the corresponding element is a “3D video left view”component.

The Component fragment (L38030) located to the right of FIG. 38 may have“bcast://lge.com/Component/3” as the ID value, and may indicate that thecorresponding component is any of the Continuous and PickOne componentsusing the ComponentType element. In addition, the Component fragment(L38030) may indicate that the corresponding component relates to theVideo component using the ComponentData element, the ContentTypeattribute, the VideoComponent element, and the VideoRole element, andmay indicate that the corresponding element is a “3D video right view”component.

FIG. 39 illustrates an XML schema of component fragments configured todescribe a Complete Audio Component according to an embodiment of thepresent invention.

In accordance with the embodiment, the Component fragment (L39010)located at the uppermost part of FIG. 39 may have“bcast://lge.com/Component/1” as the ID value, and may indicate that thecorresponding component is any of the Continuous and PickOne componentsusing the ComponentType element.

The Component fragment (L39020) located to the left side of the secondcolumn of FIG. 39 may have “bcast://lge.com/Component/2” as the IDvalue, and may indicate that the corresponding component is any of theContinuous and PickOne components using the ComponentType element. Inaddition, the Component fragment (L39020) may indicate that thecorresponding component relates to the Audio component using theComponentData element, the ContentType attribute, the AudioComponentelement, and the AudioRole element, and may indicate that thecorresponding element is a Completely Main component.

The Component fragment (L39030) located to the right part of the secondcolumn of FIG. 39 may have “bcast://lge.com/Component/3” as the IDvalue, and may indicate that the corresponding component is any of theContinuous and Composite components using the ComponentType element.

The Component fragment (L39040) located to the left side of the thirdcolumn of FIG. 39 may have “bcast://lge.com/Component/4” as the IDvalue, and may indicate that the corresponding component is any of theContinuous and PickOne components using the ComponentType element. Inaddition, the Component fragment (L39040) may indicate that thecorresponding component relates to the Audio component using theComponentData element, the ContentType attribute, the AudioComponentelement, and the AudioRole element, and may indicate that thecorresponding element is a Music component.

The Component fragment (L39050) located to the right side of the thirdcolumn of FIG. 39 may have “bcast://lge.com/Component/5” as the IDvalue, and may indicate that the corresponding component is any of theContinuous and PickOne components using the ComponentType element. Inaddition, the Component fragment (L39050) may indicate that thecorresponding component relates to the Audio component using theComponentData element, the ContentType attribute, the AudioComponentelement, and the AudioRole element, and may indicate that thecorresponding element is a Dialogue component.

FIG. 40 illustrates an XML schema of a component element contained in acontent fragment according to an embodiment of the present invention.

Referring to FIG. 40, the component contained in the content may beconstructed as the sub-element. The Component element may be containedin the Content fragment. In this case, the sub-element may have the samemeaning as the lower element.

The Component element according to one embodiment may indicate componentinformation contained in the content.

The Component element type according to one embodiment may be denoted byComponentElementType. The ComponentElementType may define componentinformation contained in the content in the form of a sequence.Therefore, all types of components contained in the content may bewritten in the ComponentElementType.

The Component element according to one embodiment may have a VideoDataelement, an AudioData element, and/or a CCData element as thesub-elements. In addition, the VideoData element may have a VideoRoleelement, a TargetUserProfile element, and/or a TargetDevice element asthe sub-elements. The AudioData element may have an AudioRole element, aTargetUserProfile element, and/or a TargetDevice element as thesub-elements. The CCData element may have a CCRole element, aTargetUserProfile element, and/or a TargetDevice element as thesub-elements. Detailed description of the above-mentioned elements hasalready been disclosed above.

FIG. 41 illustrates an XML schema of a content fragment regarding aLinear Service including Video, Audio, and CC Components according to anembodiment of the present invention.

Referring to FIG. 41, assuming that the Component element is constructedin the content fragment according to one embodiment, the Reference rulesbetween the plurality of Components need not be used, resulting inincreased efficiency. Therefore, assuming that the receiver according toone embodiment receives the content fragment, it can be recognized whichcomponent is used as the constituent element of the correspondingcontent, and it may be possible to intuitively recognize the role of therecognized component.

In accordance with the embodiment, the Component element may be definedin the PrivateExt element contained in the Content fragment.

Referring to the left side of FIG. 41 and the schema thereof, the 2Dtennis broadcast content may include Video, Audio and CC components. TheVideo component may indicate a Primary (default) video. The Audiocomponent may indicate a Complete main. The CC component may indicate anormal.

Referring to the right side of FIG. 41 and the schema thereof, the 3Dtennis broadcast content may include 2 Video components, the Audiocomponent, and a CC component. The first Video component of the 3Dtennis broadcast content may indicate a 3D video left view. The secondVideo component may indicate a 3D video right view. The Audio componentmay indicate a Complete main. The CC component may indicate a normal.

FIG. 42 illustrates an XML schema of a component element when thecomponent element is defined in the content fragment so as to describethe association relationship among Video, Audio, and CC components.

In accordance with the embodiment, it may be necessary to define theassociation relationship between constituent components of the singlecontent.

In accordance with the embodiment, assuming that the Component elementis constructed in the Content fragment, all the components (i.e., Video,Audio and/or CC components) contained in the corresponding content aredescribed in the Content fragment, such that the associationrelationship between the components need not be independently described.

FIG. 43 is a conceptual diagram illustrating an exemplary case in whichAssociatedTo attributes are used to describe the associationrelationship among Video, Audio, and CC components.

In accordance with one embodiment of the present invention, theassociatedTo attribute may be described as the Audio and CC componentattributes so as to describe the association relationship betweenPresentable Video, Audio and CC Components. As a result, if the receiveraccording to one embodiment receives the Audio component, the receivermay recognize the Video component associated with the received Audiocomponent. Likewise, if the receiver receives the CC component, thereceiver may recognize the Video component associated with the receivedCC component.

Referring to FIG. 43, the embodiment of the present invention may definethe associatedTo attribute as the attribute of the AudioComponentelement located below the ComponentData element, and may define theassociatedTo attribute as the attribute of the CCComponent element.

FIG. 44 is a conceptual diagram illustrating an exemplary case in whichassociatedAudio and associatedCC attributes are used to describe theassociation relationship among Video, Audio, and CC components.

In order to define the association relationship between PresentableVideo, Audio and CC Components, the associatedAudio and associatedCCattributes may be described (or written) as the Video component. As aresult, if the receiver according to one embodiment receives the Videocomponent, the receiver may recognize all the Audio and/or CC componentsassociated with the received Video component.

Referring to FIG. 44, the embodiment of the present invention may definethe associatedAudio and/or associatedCC attributes as the attribute ofthe VideoComponent element located below the ComponentData element, andmay define the associatedAudio and/or associatedCC attributes as theattribute of the VideoComponent element.

FIG. 45 is a conceptual diagram illustrating the associationrelationship among Video, Audio, and CC components using AssociatedToattributes.

Referring to FIG. 45, the associatedTo attribute is defined in theAudioComponent element in the Component fragment describing thePresentable Audio Component, and refers to“bcast://lge.com/Component/1”, such that the Component fragmentdescribing the Presentable Video Component associated with thecorresponding Presentable Audio Component may be signaled.

In accordance with the embodiment, the associatedTo attribute is definedin the CCComponent element in the Component fragment describing thePresentable CC Component, and refers to “bcast://lge.com/Component/1”,such that the Component fragment describing the Presentable VideoComponent associated with the corresponding Presentable CC Component maybe signaled.

FIG. 46 is a conceptual diagram illustrating the associationrelationship among Video, Audio, and CC components using associatedAudioand/or associatedCC attributes.

In accordance with the embodiment, the associatedAudio attribute and theassociatedCC attribute are defined in the VideoComponent element in theComponent fragment describing the Presentable Video Component, andrespectively refers to “bcast://lge.com/Component/2” and“bcast://lge.com/Component/3”, such that the Component fragmentsdescribing not only the Presentable Audio component associated with thecorresponding Presentable Video Component but also the Presentable CCComponent may be signaled.

FIG. 47 is a conceptual diagram illustrating the reference relationshipbetween fragments according to an embodiment of the present invention.

In accordance with one embodiment, the method for defining Service,Content, and Component fragments to provide the service guide of thenext-generation broadcast system has been disclosed.

The relationship between the above-mentioned fragments is defined, suchthat the embodiment of the present invention can provide a method forperforming announcement of the service guide for use in the nextgeneration hybrid broadcast system.

In accordance with the embodiment, the Component fragment may refer tothe Service fragment and/or the Content fragment.

Referring to FIG. 47, the Component fragment may refer to the Servicefragment and the Content fragment. The Component fragment may refer tothe Service fragment. The Schedule fragment may refer to the Service,Content, and Component fragments.

FIG. 48 illustrates an XML schema of a Component fragment including anelement indicating the reference relationship between fragmentsaccording to an embodiment of the present invention.

Referring to FIG. 48, the Component fragment may refer to theServiceReference element, the ContentReference element, and/or theComponentReference element. Each of the above-mentioned elements mayhave the idRef attribute indicating each ID.

The ServiceReference element may represent the Service fragment in thecorresponding Component fragment, and may have the ID value of thereferenced Service fragment.

The ContentReference element may represent the Content fragmentreferenced by the corresponding Component fragment, and may have an IDvalue of the referenced Content fragment.

The ComponentReference element may represent a higher Component fragmentreferenced by the corresponding Component fragment, and may have an IDvalue of the referenced higher Component fragment. In this case, thecross-reference relationship between the Component fragments or therelationship between subordinates and superiors between the Componentfragments may be established according to classification of type valuesdenoted by the above-mentioned ComponentType elements.

FIG. 49 illustrates an XML schema of a Schedule fragment including anelement indicating the reference relationship between fragmentsaccording to an embodiment of the present invention.

Referring to FIG. 49, the Schedule fragment according to one embodimentmay include the ServiceReference element, the ContentReference element,and/or the ComponentReference element. Each of the above-mentionedelements may have the idRef attribute indicating each ID.

The ServiceReference element may represent the referenced Servicefragment, and may have an ID value of the referenced Service fragment.As a result, the Schedule fragment may provide time information of thecorresponding service.

The ContentReference element may indicate the referenced Contentfragment, and may have the ID value of the referenced Content fragment.As a result, the Schedule fragment may provide time information of thecorresponding Content.

The ComponentReference element may indicate the referenced Componentfragment, and may have the ID value of the referenced Componentfragment. As a result, the Schedule fragment may provide timeinformation of the corresponding Component.

FIG. 50 illustrates the reference relationship among Service, Content,and Component fragments according to an embodiment of the presentinvention.

Referring to FIG. 50, the Component fragment describing the PresentableAudio Component and the Component fragment describing the Presentable CCComponent may refer to the other Component fragment describing thePresentable Video Component using the associatedTo attribute.

In addition, the Component fragment describing the Presentable AudioComponent, the Component fragment describing the Presentable CCComponent, and the Component fragment describing the Presentable VideoComponent may refer to the Content fragment using the ContentReferenceelement. Here, the Content fragment may have the ID value denoted by“bcast://lge.com/Content/1”.

The Content fragment in which the ID value is denoted by“bcast://lge.com/Content/1” may refer to the Service fragment in whichthe ID value is denoted by “bcast://lge.com/Service/1”, using theServiceReference element.

As described above, the embodiment of the present invention defines thecross-reference relationship between the fragments, and can constructthe service guide model capable of being provided from the hybridbroadcast system.

FIG. 51 illustrates the reference relationship among Component fragmentsconfigured to describe a Continuous Component according to an embodimentof the present invention.

The embodiment of the present invention defines the cross-referencerelationship between the component fragments, and can describe thecross-reference relationship between the Continuous Components capableof being provided from the hybrid broadcast system.

In accordance with the embodiment of the present invention, theContinuous Component may correspond to any of various components havingthe ComponentType values of 1˜6 (i.e., the Continuous component, theElementary component, the Composite component, the PickOne component,the Complex component, and/or the Presentable component). As can be seenfrom FIG. 51, the cross-reference relationship between theabove-mentioned Continuous Components can be represented.

In accordance with one embodiment of the present invention, theComponent fragment (id=“bcast://lge.com/Component/4”) describing theSecond Enhancement Layer may include “bcast://lge.com/Component/3” inthe ComponentReference element, such that the Component fragment(id=“bcast://lge.com/Component/4”) may refer to the Component fragment(id=“bcast://lge.com/Component/3”) describing the First EnhancementLayer.

As described above, since the Component fragment(id=“bcast://lge.com/Component/3”) describing the First EnhancementLayer includes “bcast://lge.com/Component/2” in the ComponentReferenceelement, the Component fragment (id=“bcast://lge.com/Component/3”) mayrefer to the component fragment (id=“bcast://lge.com/Component/2”)describing the Base layer.

In this way, the Component fragment (id=“bcast://lge.com/Component/2”)describing the Base Layer includes (“bcast://lge.com/Component/1”) inthe ComponentReference element, such that the Component fragment(id=“bcast://lge.com/Component/2”) may refer to the Component fragment(id=“bcast://lge.com/Component/1”) describing the Composite Component.

FIG. 52 illustrates the reference relationship between Componentfragments configured to describe a component associated with AppBasedEnhancement according to an embodiment of the present invention.

The embodiment of the present invention defines the cross-referencerelationship between the component fragments, such that it can describethe cross-reference relationship between the AppBased Enhancementassociated components capable of being received from the hybridbroadcast system.

In accordance with the embodiment, the components corresponding to theComponentType values of 7˜13, i.e., NRT File, NRT Content Item,Application, ATSC3.0 Application, On Demand component, NotificationStream and/or AppBased Enhancement, may correspond to the AppBasedEnhancement associated Components. As can be seen from FIG. 52, thecross-reference relationship between the above-mentioned AppBasedEnhancement associated components can be described.

In accordance with the embodiment, the component fragment(id=“bcast://lge.com/Component/3”) describing the NRT File may include“bcast://lge.com/Component/2” in the ComponentReference element, suchthat the component fragment (id=“bcast://lge.com/Component/3”) may referto the component fragment (id=“bcast://lge.com/Component/2”) describingthe NRT Content Item.

The component fragment (id=“bcast://lge.com/Component/2”) describing theNRT Content Item includes “bcast://lge.com/Component/1” in theComponentReference element, such that the component fragment(id=“bcast://lge.com/Component/2”) may refer to the component fragment(id=“bcast://lge.com/Component/1”) describing the AppBased Enhancement.

The component fragment (id=“bcast://lge.com/Component/5”) describing theOn Demand component includes “bcast://lge.com/Component/1” in theComponentReference element, such that the component fragment(id=“bcast://lge.com/Component/5”) may refer to the component fragment(id=“bcast://lge.com/Component/1”) describing the AppBased Enhancement.

The component fragment (id=“bcast://lge.com/Component/4”) describing theApplication includes “bcast://lge.com/Component/1” in theComponentReference element, such that the component fragment(id=“bcast://lge.com/Component/4”) may refer to the component fragment(id=“bcast://lge.com/Component/1”) describing the AppBased Enhancement.

FIG. 53 illustrates functions to be used when a content fragment refersto the associated service fragment according to an embodiment of thepresent invention.

When describing the Service fragment to be referenced by the Contentfragment, the embodiment of the present invention can provide a serviceguide method for describing detailed functions supported in the hybridbroadcast network.

The Content fragment according to the embodiment may have theServiceReference element. The ServiceReference element may include theidRef attribute, the weigh attribute, and/or the relationship attribute.

The idRef attribute may indicate the ID of the reference Servicefragment.

The weigh attribute may indicate importance or significance of theService fragment to be referred.

When the relationship attribute refers to the Service fragment, therelationship may indicate the relationship between the Content fragmentand the Service fragment. Further, this attribute value may berepresented by an integer value for future extensibility. If thisattribute value is set to zero ‘0’, this means ‘unspecified’. If thisattribute value is set to 1, this means ‘ProgramOf’. If this attributevalue is set to 2, this means ‘ContentItemOf’. If this attribute valueis set to 3, this means ‘OnDemandComponentOf’. If this attribute valueis set to any of the values of 4˜255, this means ‘reserved’. ProgramOfmay indicate that the corresponding content corresponds to thereferenced service program. ContentItemOf may indicate that thecorresponding content corresponds to ContentItem of the referencedservice. OnDemandComponentOf may indicate that the corresponding contentcorresponds to OnDemandComponent of the referenced service.

FIG. 54 is a conceptual diagram illustrating an exemplary case in whichthe content fragment refers to the associated service fragment using therelationship attributes according to an embodiment of the presentinvention.

When the receiver according to one embodiment of the present inventionrefers to the Service fragment using the relationship attribute, it maybe possible to recognize the relationship between both fragments.Therefore, although the embodiment does not analyze the scope extendingto the component level using the relationship attribute, the embodimentmay recognize which attribute is assigned to the content belonging tothe corresponding service, and then inform the user of the recognizedattribute information using the service guide.

Referring to FIG. 54, a total of 3 Content fragments may refer to theService fragment having the ID value denoted by“bcast://lge.com/Service/1” using the ServiceReference element. The leftcontent fragment may have the value of 1 as the relationship attributevalue, such that this means the Program of the referenced servicefragment. The intermediate content fragment has the value of 2 as therelationship attribute value, such that ContentItem of the referencedservice fragment can be indicated. The right content fragment has therelationship attribute value of 3, such that OnDemandComponent of thereferenced service fragment can be indicated.

FIG. 55 is a conceptual diagram illustrating the reference relationshipbetween fragments according to another embodiment of the presentinvention.

In accordance with one embodiment, the method for defining Service,Content, and Component fragments to provide the service guide of thenext-generation broadcast system has been disclosed.

The relationship between the above-mentioned fragments is defined, suchthat the embodiment of the present invention can provide a method forperforming announcement of the service guide for use in the nextgeneration hybrid broadcast system.

In accordance with the embodiment, the Service fragment may refer to theContent fragment and/or the Component fragment.

Referring to FIG. 55, the Service t fragment may refer to the Contentfragment and the Component fragment. The Content fragment may refer tothe Component fragment. The Schedule fragment may refer to the Service,Content, and Component fragments.

The embodiment may reduce the amount of resources needed to search notonly for the constituent content of a specific service but also for thecomponent element.

FIG. 56 is a conceptual diagram illustrating a service fragmentincluding not only elements indicating the reference relationshipbetween fragments, but also a content fragment and an XML schema of thecomponent fragment according to another embodiment of the presentinvention.

Referring to FIG. 56, the cross-reference relationship may be achievedbetween the respective fragments of the service guide according to theembodiment.

The service fragment according to one embodiment may include theContentReference element and/or the ComponentReference element. Each ofthe above-mentioned elements may have the idRef attribute indicatingeach ID. (L56010)

The ContentReference element may represent the Content fragment in thecorresponding Component fragment, and may have the ID value of thereferenced Content fragment.

The ContentReference element may represent the Component fragmentreferenced by the corresponding Service fragment, and may have an IDvalue of the referenced Component fragment.

The Content fragment according to the embodiment may include theComponentReference element. The ComponentReference element may have theidRef attribute indicating the ID of this element. (L56020)

The ComponentReference element may represent the Component fragmentreferenced by the corresponding content fragment, and may have the IDvalue of the referenced component fragment.

The Component fragment according to the embodiment may include theComponentReference element. This Component fragment may have the idRefattribute indicating the ID of this element. (L56030)

The ComponentReference element may represent a lower Component fragmentreferenced by the corresponding Component fragment, and may have an IDvalue of the referenced lower Component fragment. In this case, thecross-reference relationship between the Component fragments or therelationship between subordinates and superiors between the Componentfragments may be established according to classification of type valuesdenoted by the above-mentioned ComponentType elements.

The Schedule fragment according to one embodiment may include theServiceReference element, the ContentReference element, and/or theComponentReference element. Each of the above-mentioned elements mayhave the idRef attribute indicating each ID. (not shown)

The ServiceReference element may represent the referenced Servicefragment, and may have an ID value of the referenced Service fragment.As a result, the Schedule fragment may provide time information of thecorresponding service.

ContentReference element may indicate the referenced Content fragment,and may have the ID value of the referenced Content fragment. As aresult, the Schedule fragment may provide time information of thecorresponding Content.

The ComponentReference element may indicate the referenced Componentfragment, and may have the ID value of the referenced Componentfragment. As a result, the Schedule fragment may provide timeinformation of the corresponding Component.

FIG. 57 is a conceptual diagram illustrating the reference relationshipbetween Service, Content and Component fragments according to anotherembodiment of the present invention.

Referring to FIG. 57, the Component fragment describing the PresentableAudio Component and the Component fragment describing the Presentable CCComponent may refer to the other component describing the PresentableVideo Component using the associatedTo attribute.

The Service fragment in which the ID value is denoted by“bcast://lge.com/Service/1” may refer to the Content fragment in whichthe ID value is denoted by “bcast://lge.com/Content/1”, using theContentReference element.

The Service fragment in which the ID value is denoted by“bcast://lge.com/Content/1” may refer to the Content fragment in whichthe ID value is denoted by “bcast://lge.com/Component/1”, using theComponentReference element.

As described above, the embodiment of the present invention defines thecross-reference relationship between the fragments, and can constructthe service guide model capable of being provided from the hybridbroadcast system.

The embodiment of the present invention uses the reference directionranging from the higher layer to the lower level in the same manner asin the above-mentioned method in which the Service fragment refers tothe content fragment and the Content fragment refers to the componentfragment, such that the embodiment shown in FIG. 57 can greatly reducethe amount of resources to be consumed.

FIG. 58 is a conceptual diagram illustrating the reference relationshipbetween Component fragments describing a Continuous Component accordingto another embodiment of the present invention.

The embodiment of the present invention defines the cross-referencerelationship between the component fragments, and can describe thecross-reference relationship between the Continuous Components capableof being provided from the hybrid broadcast system.

In accordance with the embodiment of the present invention, theContinuous Component may correspond to any of various components havingthe ComponentType values of 1˜6 (i.e., the Continuous component, theElementary component, the Composite component, the PickOne component,the Complex component, and/or the Presentable component). As can be seenfrom FIG. 58, the cross-reference relationship between theabove-mentioned Continuous Components can be represented.

In accordance with one embodiment of the present invention, theComponent fragment (id=“bcast://lge.com/Component/1”) describing theComposite Component may include “bcast://lge.com/Component/2” in theComponentReference element, such that the Component fragment(id=“bcast://lge.com/Component/1”) may refer to the Component fragment(id=“bcast://lge.com/Component/2”) describing the Base Layer.

As described above, since the Component fragment(id=“bcast://lge.com/Component/2”) describing the Base Layer includes“bcast://lge.com/Component/2” in the ComponentReference element, theComponent fragment (id=“bcast://lge.com/Component/2”) may refer to thecomponent fragment (id=“bcast://lge.com/Component/3”) describing theFirst Enhancement layer.

Likewise, the Component fragment (id=“bcast://lge.com/Component/3”)describing the First Enhancement Layer includes(“bcast://lge.com/Component/4”) in the ComponentReference element, suchthat the Component fragment (id=“bcast://lge.com/Component/3”) may referto the Component fragment (id=“bcast://lge.com/Component/4”) describingthe Second Enhancement Layer.

FIG. 59 is a conceptual diagram illustrating the reference relationshipbetween Component fragments describing a component associated withAppBased Enhancement according to another embodiment of the presentinvention.

The embodiment of the present invention defines the cross-referencerelationship between the component fragments, such that it can describethe cross-reference relationship between the AppBased Enhancementassociated components capable of being received from the hybridbroadcast system.

In accordance with the embodiment, the components corresponding to theComponentType values of 7˜13, i.e., NRT File, NRT Content Item,Application, ATSC3.0 Application, On Demand component, NotificationStream and/or AppBased Enhancement, may correspond to the AppBasedEnhancement associated Components. As can be seen from FIG. 59, thecross-reference relationship between the above-mentioned AppBasedEnhancement associated components can be described.

In accordance with the embodiment, the Component fragment(id=“bcast://lge.com/Component/1”) describing the AppBased Enhancementmay include “bcast://lge.com/Component/2”,“bcast://lge.com/Component/4”, and “bcast://lge.com/Component/5” in theComponentReference element, such that the Component fragment(id=“bcast://lge.com/Component/1”) may refer to the component fragment(id=“bcast://lge.com/Component/2”) describing the NRT Content Item, thecomponent fragment (id=“bcast://lge.com/Component/4”) describing theApplication, and the component fragment(id=“bcast://lge.com/Component/5”) describing the OnDemand component.

The component fragment (id=“bcast://lge.com/Component/2”) describing theNRT Content Item includes “bcast://lge.com/Component/3” in theComponentReference element, such that the component fragment(id=“bcast://lge.com/Component/2”) may refer to the component fragment(id=“bcast://lge.com/Component/3”) describing the NRT File.

FIGS. 60 and 61 illustrate the Component fragments according to anembodiment of the present invention.

It should be noted that Table of FIG. 60 and Table of FIG. 61 aregrouped into one table such that two tables shown in FIGS. 60 and 61 maycorrespond to one table.

The component fragment according to the embodiment may include an idattribute, a version attribute, a validFrom attribute, a validToattribute, a ServiceReference element, a ContentReference element,ComponentReference element, a ComponentType element, a ComponentRoleelement, a PrivateExt element, and/or a ProprietaryElements element.Each of the ServiceReference element, the ContentReference element, andthe ComponentReference element may include the idRef attribute. Theabove-mentioned id attribute and/or the idRef attribute may include theURI format, and the above-mentioned attribute and/or elements willhereinafter be described.

FIG. 62 illustrates an XML schema of a Component fragment according toanother embodiment of the present invention.

Referring to FIG. 62, the Component fragment according to one embodimentmay describe some parts of content to be referenced by the component, ormay describe some parts of the service to be referenced by thecomponent. (The ‘Component’ fragment describes a component that is apart of a service or a content that the component refers to.)

The Component fragment according to the embodiment may include an idattribute, a version attribute, a validFrom attribute, a validToattribute, a ServiceReference element, a ContentReference element, aComponentReference element, a ComponentType element, a ComponentRoleelement, a PrivateExt element, and/or a ProprietaryElements element.

The ‘id’ attribute may indicate an ID of the component fragment. Thisattribute value may be globally unique.

The version attribute may indicate version information of the componentfragment.

The validFrom attribute may indicate an initial time at which thecomponent fragment is valid.

The validTo attribute may denote the last time at which the componentfragment is valid.

The ServiceReference element may refer to the service fragment includingthe corresponding component.

The ContentReference element may refer to the Content fragment includingthe corresponding component.

The ComponentReference element may refer to the component fragmentincluding the corresponding component.

The ComponentType element may indicate the content type denoted by theComponent fragment. If the types are mixed with each other, theComponentType element may indicate the type using one or moreComponentType element.

The ComponentRole element may indicate the role of the correspondingcomponent. In accordance with the embodiment of the present invention,if the corresponding component is set to the Presentable Video, theComposite Video, the Presentable Audio, or the Presentable CC component,the ComponentRole element may include the Component Role, and a detaileddescription of the ComponentRole is as follows.

The PrivateExt element may indicate a container for proprietary orapplication-specified extension. (The PrivateExt element may serve as acontainer for proprietary or applicationspecific extensions).

The ProprietaryElements element may indicate proprietary orapplication-specific elements. The ProprietaryElements element mayinclude one or more sub-elements or one or more attributes.

FIG. 63 illustrates an XML schema of a ComponentType element accordingto another embodiment of the present invention.

Referring to FIG. 63, the component according to the embodiment mayrepresent all the ComponentType elements capable of being transmittedthrough hybrid broadcasting. For this purpose, the range of the type maybe represented by an integer value.

In accordance with the embodiment, not all the components include data(ComponentData), such that the reception apparatus can first recognizethe type value of the component fragment, and then recognize informationregarding component data.

The relationship between subordinates and superiors of the components orthe subordinate relationship of the respective components willhereinafter be given.

In accordance with the embodiment, the ComponentRangeType indicating theComponentType element type may be set to zero as a minimum value, andmay be set to 15 as a maximum value.

As shown in FIG. 63, if the ComponentType element value is set to zero,this means ‘Unspecified’. If the ComponentType element value is set to1, this means a Continuous component. If the ComponentType element valueis set to 2, this means an Elementary component. If the ComponentTypeelement value is set to 3, this means a Composite component. If theComponentType element value is set to 4, this means a PickOne component.If the ComponentType element value is set to 5, this means a Complexcomponent. If the ComponentType element value is set to 6, this means aPresentable Audio component. If the ComponentType element value is setto 7, this means a Presentable Audio component. If the ComponentTypeelement value is set to 8, this means a Presentable CC component. If theComponentType element value is set to 9, this means an NRT File. If theComponentType element value is set to 10, this means an NRT ContentItem. If the ComponentType element value is set to 11, this means anApplication. If the ComponentType element value is set to 12, this meansan ATSC3.0 Application. If the ComponentType element value is set to 13,this means an On Demand component. If the ComponentType element value isset to 14, this means a Notification Stream. If the ComponentTypeelement value is set to 15, this means an AppBased Enhancement. If theComponentType element value is set to any one of 16 to 255, this means‘Reserved’.

The Continuous component may indicate a content component represented inone continuous stream. For example, the Continuous component maycorrespond to Audio, Video, or Closed Caption.

The Elementary component may indicate a Continuous componentcorresponding to single encoding. That is, the Elementary component mayindicate a Continuous component encoded by a separate encoder. Forexample, single encoding of the sound sequence, single encoding of thepicture sequence, or the single closed caption track may correspond tothe Elementary component.

The Composite component may indicate a content component constructingthe set of continuous components which have the same content type,represent the same scene, and can be combined to construct onepresentation. For example, the Composite component may be implemented asmusic, dialogue, and sound effect, which are to be mixed to providehigh-quality audio. In addition, a left-eye image and a right-eye imageto be combined to construct a three dimensional (3D) image may alsocorrespond to the composite component.

The PickOne component may indicate a content component constructing theset of continuous components capable of being selected to have the samecontent type, display the same scene, and construct one presentation.For example, the set of audio components encoded by bit rates differentfrom those of the same sound sequence, the set of video componentsencoded by bit rates different from those of the same picture sequence,or the set of general closed caption tracks and easy reader closedcaption tracks for the same dialogue may correspond to the PickOnecomponent.

The Complex component may indicate the Composite component or thePickOne component.

The Presentable component may denote the Continuous component displayedfor the user. The Presentable component may include the Elementarycomponent or Complex component.

The Presentable Video component may denote the Video Continuouscomponent displayed for the user.

The Presentable Audio component may denote the Audio Continuouscomponent displayed for the user.

The Presentable CC component may denote the CC Continuous componentdisplayed for the user.

The NRT File may indicate a non-realtime transmission file.

The NRT Content Item may indicate the set of one or more NRT files to bepackage-consumed by users who will purchase the set of NRT files.

The Application may indicate the set of constituent documents of thecomplete enhanced or interactive service. The above-mentioned documentsmay include HTML, JavaScript, CSS, XML, and/or multimedia files. TheApplication may access another data instead of the part of theapplication. This Application may correspond to a special case of NRTContent Item.

The ATSC3.0 Application may indicate Application based on ATSC 3.0Application Runtime Environment Specification.

The On Demand component may indicate a content component transmitted ondemand.

The Notification Stream may indicate a stream capable of transmitting anotification message configured to synchronize actions of theapplication under Linear Time Base.

The AppBased Enhancement may include zero or more Notification Streamsto transmit synchronized notification of the actions, one or moreapplications, zero or more different NRT Content Items used by theapplication, and zero or more On Demand components managed by theapplication.

FIG. 64 illustrates an XML schema of a ComponentRole element accordingto an embodiment of the present invention.

Referring to FIG. 64, the component may indicate the role of all thecomponents capable of being transmitted through hybrid broadcasting. Forthis purpose, the ComponentRole element may be denoted by an integervalue.

The ComponentRole element may range from 0 to 21.

The Component element ranges from 0 to 21 such that it can indicate notonly the role obtained when the Component element is ‘Presentable’, butalso the role obtained when the Component element is ‘Composite’.

If the ComponentRole element according to the embodiment is denoted by0, this means ‘Unspecified’. If the ComponentRole element is denoted by1, this means ‘Primary (default) video’. If the ComponentRole element isdenoted by 2, this means ‘Alternative camera view’. If the ComponentRoleelement is denoted by 3, this means ‘Other alternative video component’.If the ComponentRole element is denoted by 4, this means ‘Sign language(e.g., ASL) inset’. If the ComponentRole element is denoted by 5, thismeans ‘Follow subject video’. If the ComponentRole element is denoted by6, this means ‘Base layer for scalable video encoding’. If theComponentRole element is denoted by 7, this means ‘Enhancement layer forscalable video encoding with level’. If the ComponentRole element isdenoted by 8, this means ‘3D video left view’. If the ComponentRoleelement is denoted by 9, this means ‘3D video right view’. If theComponentRole element is denoted by 10, this means ‘3D video depthinformation’. If the ComponentRole element is denoted by 11, this means‘Part of video array, <x,y> of <n,m>. If the ComponentRole element isdenoted by 12, this means ‘FollowSubject metadata’. If the ComponentRoleelement is denoted by 13, this means ‘Complete main’. If theComponentRole element is denoted by 14, this means ‘Music’. If theComponentRole element is denoted by 15, this means ‘Dialogue’. If theComponentRole element is denoted by 16, this means ‘Effects’. If theComponentRole element is denoted by 17, this means ‘Visually impaired’.If the ComponentRole element is denoted by 18, this means ‘Hearingimpaired’. If the ComponentRole element is denoted by 19, this means‘Commentary’. If the ComponentRole element is denoted by 20, this means‘Normal’. If the ComponentRole element is denoted by 21, this means‘Easy reader’. If the ComponentRole element is denoted by 22˜255, thismeans ‘Reserved’. If the ComponentRole element is denoted by 1˜5, thismeans the role of a presentable Video Component. If the ComponentRoleelement is denoted by 6˜12, this means the role of a Composite VideoComponent. If the ComponentRole element is denoted by 13˜19, this meansthe role of a presentable Audio Component. If the ComponentRole elementis denoted by 20˜21, this means the role of a presentable CC Component.

FIG. 65 illustrates an XML schema of component fragments regarding aComposite Video Component including one base layer and two enhancementlayers in scalable video coding according to another embodiment of thepresent invention.

In accordance with the embodiment, the Component fragment (L65010)located at the top of FIG. 65 may have the ID value“bcast://lge.com/Component/1”, may refer to the Service1 using theServiceReference element, may refer to the Content1 using theContentReference element, and may indicate that the correspondingcomponent is any of the Continuous and Composite components using theComponentType element.

The Component fragment (L65020) located to the left of FIG. 65 may have“bcast://lge.com/Component/2” as the ID value, may refer to the Service1using the ServiceReference element, may refer to the Content1 using theContentReference element, may refer to “bcast://lge.com/Component/1”using the ComponentReference element, and may indicate that thecorresponding element is Continuous, Elementary, and Base Layer of SVCcomponents using the ComponentType element.

The Component fragment (L65030) located to the right of FIG. 65 may have“bcast://lge.com/Component/3” as the ID value, may refer to the Service1using the ServiceReference element, may refer to the Content1 using theContentReference element, may refer to “bcast://lge.com/Component/1”using the ComponentReference element, and may indicate that thecorresponding element is Continuous, Elementary, and Enhancement Layerof SVC components using the ComponentType element.

FIG. 66 illustrates an XML schema of component fragments regarding aComposite Component including a 3D video left view and a 3D video rightview according to an embodiment of the present invention.

In accordance with the embodiment, the Component fragment (L66010)located at the top of FIG. 66 may have the ID value“bcast://lge.com/Component/1”, may refer to the Service1 using theServiceReference element, may refer to the Content1 using theContentReference element, and may indicate that the correspondingcomponent is any of the Continuous and Composite components using theComponentType element.

The Component fragment (L66020) located to the left of FIG. 66 may have“bcast://lge.com/Component/2” as the ID value, may refer to the Service1using the ServiceReference element, may refer to the Content1 using theContentReference element, may refer to “bcast://lge.com/Component/1”using the ComponentReference element, and may indicate that thecorresponding element is Continuous, PickOne, and 3D video left viewcomponents using the ComponentType element.

The Component fragment (L66030) located to the right of FIG. 66 may have“bcast://lge.com/Component/3” as the ID value, may refer to the Service1using the ServiceReference element, may refer to the Content1 using theContentReference element, may refer to “bcast://lge.com/Component/1”using the ComponentReference element, and may indicate that thecorresponding element is Continuous, PickOne, and 3D video right viewcomponents using the ComponentType element.

FIG. 67 illustrates an XML schema of component fragments configured todescribe a Complete Audio Component according to another embodiment ofthe present invention.

In accordance with the embodiment, the Component fragment (L67010)located at the uppermost part of FIG. 67 may have the ID value“bcast://lge.com/Component/1”, may refer to the Service1 using theServiceReference element, may refer to the Content1 using theContentReference element, and may indicate that the correspondingcomponent is any of the Continuous and PickOne components using theComponentType element.

The Component fragment (L67020) located to the left side of the secondcolumn of FIG. 67 may have “bcast://lge.com/Component/2” as the IDvalue, may refer to the Service1 using the ServiceReference element, mayrefer to the Content1 using the ContentReference element, may refer to“bcast://lge.com/Component/1” using the ComponentReference element, andmay indicate that the corresponding element is Continuous, PickOne, andAudio Completely Main components using the ComponentType element.

The Component fragment (L67030) located to the right side of the secondcolumn of FIG. 67 may have “bcast://lge.com/Component/3” as the IDvalue, may refer to the Service1 using the ServiceReference element, mayrefer to the Content1 using the ContentReference element, may refer to“bcast://lge.com/Component/1” using the ComponentReference element, andmay indicate that the corresponding element is Continuous and Compositecomponents using the ComponentType element.

The Component fragment (L67040) located to the left side of the thirdcolumn of FIG. 67 may have “bcast://lge.com/Component/4” as the IDvalue, may refer to the Service1 using the ServiceReference element, mayrefer to the Content1 using the ContentReference element, may refer to“bcast://lge.com/Component/3” using the ComponentReference element, andmay indicate that the corresponding element is Continuous, PickOne, andAudio Music components using the ComponentType element.

The Component fragment (L67050) located to the right side of the thirdcolumn of FIG. 67 may have “bcast://lge.com/Component/5” as the IDvalue, may refer to the Service1 using the ServiceReference element, mayrefer to the Content1 using the ContentReference element, may refer to“bcast://lge.com/Component/3” using the ComponentReference element, andmay indicate that the corresponding element is Continuous, PickOne, andAudio Music components using the ComponentType element.

FIG. 68 is a structural view illustrating a Content fragment accordingto an embodiment of the present invention.

Referring to FIG. 68, the embodiment of the present invention canprovide a method for defining the component as a lower element of theContent fragment, and announcing the defined result to the device anduser.

In accordance with the embodiment of the present invention, thecomponent fragment is constructed separately, such that it can reducethe number of unavoidable overlapping or repeated use times of theconstituent elements and/or attributes. In addition, the embodiment canintuitively provide the user with announcement information.

The Content fragment according to the embodiment may include the idattribute, the version attribute, the validFrom attribute, validToattribute, the globalContentID attribute, the emergency attribute, thebaseCID attribute, the ServiceReference element, the ProtectionKeyIDelement, the Name element, the Description element, the StartTimeelement, the EndTime element, the AudioLanguage element, theTextLanguage element, the Length element, the ParentalRating element,the TargetUserProfile element, the Genre element, the Extension element,the PreviewDataReference element, the Broadcast Area element, theTermsOfUse element, and/or the PrivateExt element.

The id attribute may indicate an ID of the Content fragment.

The version attribute may indicate version information of the componentfragment.

The validFrom attribute may indicate an initial time at which thecomponent fragment is valid.

The validTo attribute may denote the last time at which the componentfragment is valid.

The globalContentID attribute may indicate the ID for identifying thecontent describing the corresponding content fragment.

The emergency attribute may indicate whether the content described bythe corresponding content fragment is an emergency content.

The baseCID attribute may indicate the CID information of the service orprogram.

The ServiceReference element may indicate the service referenced by thecorresponding content fragment.

The ProtectionKeyID element may indicate the Key identifier needed toaccess the protected content.

The Name element may indicate the name of the corresponding contentfragment.

The Description element may indicate Description of the correspondingcontent fragment.

The StartTime element may indicate the start time information of thecorresponding content presentation.

The EndTime element may indicate the end time information forpresentation of the corresponding content.

The AudioLanguage element may allow the corresponding content to be usedalong with the audio stream. In this case, the AudioLanguage element mayindicate language information of the used audio.

The TextLanguage element may allow the corresponding content of be usedalong with the text component. In this case, the TextLanguage elementmay indicate language information of the used text.

The Length element may represent the duration time of the correspondingA/V content.

The ParentalRating element may represent reference informationindicating whether the corresponding content is appropriate forchildren.

The TargetUserProfile element may represent information regarding thetarget user.

The Genre element may represent genre information of the correspondingcontent.

The Extension element may represent additional information related tothe corresponding content fragment.

The PreviewDataReference element may represent the PreviewData fragmentreferenced by the corresponding component fragment.

The BroadcastArea element may represent broadcast regional informationincluding the position information for the broadcast content.

The TermsOfUse element may represent ‘Terms of User’ related to thecorresponding fragment.

The PrivateExt element may represent a container for proprietary orapplication specific extensions. (An element serving as a container forproprietary or application-specific extensions.) The PrivateExt elementmay include the ProprietaryElements element as the sub-element. TheProprietaryElements element may represent the proprietary element or theapplication specific element. The ProprietaryElements element mayinclude one or more sub-elements or one or more attributes.

Since the PrivateExt element of the content fragment according to oneembodiment is an element having an E1 level, the component elementacting as the sub-element of the PrivateExt element may correspond tothe E2 level. In this case, the component element may correspond to theabove-mentioned ProprietaryElements element.

FIGS. 69, 70, 71, and 72 are structural views illustrating Componentelements according to an embodiment of the present invention.

It should be noted that Tables of FIGS. 69 to 72 are grouped into onetable such that four tables shown in FIGS. 69 to 72 may correspond toone table.

The component element according to the embodiment may correspond to theE2-level element, and can describe detailed information of thecomponent. As a result, as many component elements as the number ofcomponent may be present or absent. Accordingly, the above-mentionedcomponent element may have cardinality ranging from 0 to N.

The Component element according to one embodiment may include theComponentType element, the ComponentRole element, the StartTime element,the EndTime element, the Language element, the Length element, theParentalRating element, the DeviceCapability element, and/or theTargetDevice element, as the sub-elements.

The ComponentType element may describe the component type. ThisComponentType element is located below the component element, such thatit may correspond to the E3 level. The ComponentType element is anessential element indicating the type of the component element, suchthat the ComponentType element may be set to 1. If the ComponentTypeelement is set to zero, this means an unspecified component. If theComponentType element is set to 1, this means a Presentable Videocomponent. If the ComponentType element is set to 2, this means aPresentable Audio component. If the ComponentType element is set to 3,this means a Presentable CC component. If the ComponentType element isset to 4, this means an AppBased Enhancement element. If theComponentType element is set to 2, this means an AppBased Enhancement.If the ComponentType element is set to the values of 5 to 22, this meansa Reserved for future use.

The ComponentRole element may be used to describe the role of eachcomponent. The ComponentRole element is located below the componentelement, such that it may correspond to an E3 level. Since theComponentRole element is an essential element describing the type of thecomponent element, it has the cardinality of 1. Each component has therole according to the above-mentioned ComponentType element type, andmay have the role corresponding to the ComponentRole element value. Ifthe ComponentRole element is set to zero, this means an Unspecified. Ifthe ComponentRole element is set to 1, this means a Primary (default)video. If the ComponentRole element is set to 2, this means anAlternative camera view. If the ComponentRole element is set to 3, thismeans an Alternative video component. If the ComponentRole element isset to 4, this means a Sign language (e.g., ASL) inset. If theComponentRole element is set to 5, this means a Follow subject video. Ifthe ComponentRole element is set to 6, this means a Complete main. Ifthe ComponentRole element is set to 7, this means ‘Music’. If theComponentRole element is set to 8, this means ‘Dialogue’. If theComponentRole element is set to 9, this means ‘Effects’. If theComponentRole element is set to 10, this means ‘Visually impaired’. Ifthe ComponentRole element is set to 1, this means ‘Hearing impaired’. Ifthe ComponentRole element is set to 12, this means ‘Commentary’. If theComponentRole element is set to 13, this means ‘Normal’. If theComponentRole element is set to 14, this means an Easy reader. If theComponentRole element is set to 15, this means ‘App’. If theComponentRole element is set to 16, this means an NRT Content Item. Ifthe ComponentRole element is set to 17, this means an On Demandcomponent. If the ComponentRole element is set to 18, this means aNotification Stream. If the ComponentRole element is set to 19, thismeans a StartOver. If the ComponentRole element is set to 20, this meansa Companion Screen. If the ComponentRole element is set to the values of21 to 255, this means a Reserved for future use.

The StartTime element may represent a start time at which the display ofthe corresponding component starts displaying.

The EndTime element may represent the end time of the display operationof the corresponding component.

The Language element may represent expression language of thecorresponding component. The Language element may have thelanguageSDPTag attribute as the attribute value. The languageSDPTagattribute may represent a value tagged to achieve consistency oflanguages described in the session description.

The Length element may represent the duration time during whichdisplaying of the corresponding component is performed.

The ParentalRating element may represent the rating display informationof the corresponding component.

The DeviceCapability element may represent throughput or performanceinformation of the device configured to perform rendering of thecorresponding component. The embodiment may provide capabilityinformation of the device configured to perform rendering of thecomponent using the DeviceCapability element. The DeviceCapabilityelement having the values of 2 to 8 may represent Video RenderingCapability information of the device. The DeviceCapability elementhaving the values of 9 to 15 may represent Audio Surround SoundCapability information of the device. The DeviceCapability elementhaving the value of 16 may represent the Audio Surround SoundCapability. The DeviceCapability element having the values of 17 to 21may represent the Input Capability information. If the DeviceCapabilityelement is set to zero ‘0’, this means an Unspecified. If theDeviceCapability element is set to 1, this means Broadband connection.If the DeviceCapability element is set to 2, this means ‘SD’. If theDeviceCapability element is set to 3, this means ‘HD’. If theDeviceCapability element is set to 4, this means ‘UHD’. If theDeviceCapability element is set to 5, this means ‘8K’. If theDeviceCapability element is set to 6, this means ‘3D video’. If theDeviceCapability element is set to 7, this means ‘High Dynamic RangeImaging’. If the DeviceCapability element is set to 8, this means ‘WideColor Gamut’. If the DeviceCapability element is set to 9, this means‘2.0 channels’. If the DeviceCapability element is set to 10, this means‘2.1 channels’. If the DeviceCapability element is set to 11, this means‘5.1 channels’. If the DeviceCapability element is set to 12, this means‘6.1 channels’. If the DeviceCapability element is set to 13, this means‘7.1 channels’. If the DeviceCapability element is set to 14, this means‘22.1 channels’. If the DeviceCapability element is set to 15, thismeans 3D audio. If the DeviceCapability element is set to 16, this meansDialog Level adjustment. If the DeviceCapability element is set to 17,this means a magic remote control input. If the DeviceCapability elementis set to 18, this means a touch screen input. If the DeviceCapabilityelement is set to 19, this means a mouse input. If the DeviceCapabilityelement is set to 20, this means a keyboard use. In this case, theabove-mentioned broadband connection may indicate whether broadbandconnection is needed to deliver the corresponding component. The VideoRendering Capability information may represent Resolution, 2D, 3D and/orother rendering associated information. The Audio Surround SoundCapability information may represent audio channel information. Dialoglevel adjustment of the Audio Mixing/Rendering Capability informationmay indicate whether the audio dialogue level can be adjusted. The InputCapability information may indicate a broadcast program manufacturedaccording to a specific input device. The ‘app rendering’ informationmay indicate whether the app rendering is needed.

The TargetDevice element may represent information of the target deviceon which the component is displayed. If the TargetDevice element is setto zero, this means ‘Unspecified’. If the TargetDevice element is set to1, this means ‘Primary’. If the TargetDevice element is set to 2, thismeans ‘Companion’. If the TargetDevice element is set to 3, this means‘Inset on Primary Screen (“PictureinPicture”)’. If the TargetDeviceelement is set to 4, this means ‘Reserved for future use’.

FIG. 73 illustrates an XML schema of a Component element according to anembodiment of the present invention.

Referring to FIG. 73, the Component element according to one embodimentof the present invention may include, as the sub-elements, theComponentType element, the ComponentRole element, the StartTime element,the EndTime element, the Language element, the Length element, theParentalRating element, the DeviceCapability element, and/or theTargetDevice element. Detailed description of the above-mentionedelements has already been disclosed.

FIG. 74 illustrates an XML schema of a Language element and aComponentType element according to an embodiment of the presentinvention.

The Language element according to one embodiment may representexpression language of the corresponding component. The Language elementmay have the languageSDPTag attribute as the attribute. ThelanguageSDPTag attribute may represent a specific value tagged toachieve consistency of languages described in the session description.(L74010)

The ComponentType element according to one embodiment may be an elementto describe the component type. The ComponentType element is locatedbelow the component element, such that it may correspond to an E3 level.Since the ComponentType element is an essential element to describe thetype of the component element, the ComponentType element may havecardinality of 2. If the ComponentType element is set to zero, thismeans an Unspecified. If the ComponentType element is set to 1, thismeans a Presentable Video component. If the ComponentType element is setto 2, this means a Presentable Audio component. If the ComponentTypeelement is set to 3, this means a Presentable CC component. If theComponentType element is set to 4, this means an AppBased Enhancement.If the ComponentType element is set to the values of 5 to 255, thismeans a Reserved for future use.

FIG. 75 illustrates an XML schema of a ComponentRole element accordingto an embodiment of the present invention.

Referring to FIG. 75, the ComponentRole element may be an element todescribe the Role of the component. Since the ComponentRole element islocated below the component element, it may correspond to an E3 level.Since the ComponentRole element is an essential element to describe thetype of the component element, the ComponentRole element may havecardinality of 1. Each component may have the role according to theabove-mentioned ComponentType element types, and may also have the rolecorresponding to the ComponentRole element value. If the ComponentRoleelement is set to zero, this means an unspecified. If the ComponentRoleelement is set to 1, this means a Primary (default) video. If theComponentRole element is set to 2, this means an Alternative cameraview. If the ComponentRole element is set to 3, this means otheralternative video component. If the ComponentRole element is set to 4,this means a Sign language (e.g., ASL) inset. If the ComponentRoleelement is set to 5, this means a Follow subject video. If theComponentRole element is set to 6, this means a Complete main. If theComponentRole element is set to 7, this means a Music. If theComponentRole element is set to 8, this means a Dialogue. If theComponentRole element is set to 9, this means Effects. If theComponentRole element is set to 10, this means a Visually impaired. Ifthe ComponentRole element is set to 11, this means a Hearing impaired.If the ComponentRole element is set to 12, this means a Commentary. Ifthe ComponentRole element is set to 13, this means a Normal. If theComponentRole element is set to 14, this means an Easy reader. If theComponentRole element is set to 15, this means ‘App’. If theComponentRole element is set to 16, this means an NRT Content Item. Ifthe ComponentRole element is set to 17, this means an On Demandcomponent. If the ComponentRole element is set to 18, this means aNotification Stream. If the ComponentRole element is set to 19, thismeans a StartOver. If the ComponentRole element is set to 20, this meansa Companion Screen. If the ComponentRole element is set to the values of21 to 255, this means a Reserved for future use.

FIG. 76 illustrates an XML schema of a DeviceCapability element and aTargetDevice element according to an embodiment of the presentinvention.

Referring to FIG. 76, the DeviceCapability element may representthroughput or performance information of the device configured toperform rendering of the corresponding component. The embodiment mayprovide capability information of the device configured to performrendering of the component using the DeviceCapability element. TheDeviceCapability element having the values of 2 to 8 may represent VideoRendering Capability information of the device. The DeviceCapabilityelement having the values of 9 to 15 may represent Audio Surround SoundCapability information of the device. The DeviceCapability elementhaving the value of 16 may represent the Audio Surround SoundCapability. The DeviceCapability element having the values of 17 to 21may represent the Input Capability information. If the DeviceCapabilityelement is set to zero ‘0’, this means an Unspecified. If theDeviceCapability element is set to 1, this means Broadband connection.If the DeviceCapability element is set to 2, this means ‘SD’. If theDeviceCapability element is set to 3, this means ‘HD’. If theDeviceCapability element is set to 4, this means ‘UHD’. If theDeviceCapability element is set to 5, this means ‘8K’. If theDeviceCapability element is set to 6, this means ‘3D video’. If theDeviceCapability element is set to 7, this means ‘High Dynamic RangeImaging’. If the DeviceCapability element is set to 8, this means ‘WideColor Gamut’. If the DeviceCapability element is set to 9, this means‘2.0 channels’. If the DeviceCapability element is set to 10, this means‘2.1 channels’. If the DeviceCapability element is set to 11, this means‘5.1 channels’. If the DeviceCapability element is set to 12, this means‘6.1 channels’. If the DeviceCapability element is set to 13, this means‘7.1 channels’. If the DeviceCapability element is set to 14, this means‘22.1 channels’. If the DeviceCapability element is set to 15, thismeans 3D audio. If the DeviceCapability element is set to 16, this meansDialog Level adjustment. If the DeviceCapability element is set to 17,this means a magic remote control input. If the DeviceCapability elementis set to 18, this means a touch screen input. If the DeviceCapabilityelement is set to 19, this means a mouse input. If the DeviceCapabilityelement is set to 20, this means a keyboard use. In this case, theabove-mentioned broadband connection may indicate whether broadbandconnection is needed to deliver the corresponding component. The VideoRendering Capability information may represent Resolution, 2D, 3D and/orother rendering associated information. The Audio Surround SoundCapability information may represent audio channel information. Dialoglevel adjustment of the Audio Mixing/Rendering Capability informationmay indicate whether the audio dialogue level can be adjusted. The InputCapability information may indicate a broadcast program manufacturedaccording to a specific input device. The ‘app rendering’ informationmay indicate whether the app rendering is needed. (L76010)

The TargetDevice element may represent information of the target deviceon which the component is displayed. If the TargetDevice element is setto zero, this means ‘Unspecified’. If the TargetDevice element is set to1, this means ‘Primary’. If the TargetDevice element is set to 2, thismeans ‘Companion’. If the TargetDevice element is set to 3, this means‘Inset on Primary Screen (“PictureinPicture”)’. If the TargetDeviceelement is set to 4, this means ‘Reserved for future use’. (L76020)

FIG. 77 illustrates an XML schema of a Component element when aPresentable Video Component (2D/HD) and a Presentable Audio Component(5.1 channels) are transmitted.

Referring to FIG. 77, according to one embodiment, if the PresentableVideo Component (2D/HD) and presentable Audio Component (5.1 channels)are transmitted, the announcement function may use two Componentelements as the sub-element of the PrivateExt element contained in theContent fragment. (L77010)

The component element for the Presentable Video Component (2D/HD) mayhave the value of 1 (i.e., Video) as the ComponentType element value,may have the value of 1 (i.e., Primary Video) as the ComponentRoleelement value, may have the value of 3 (i.e., HD) as theDeviceCapability element value, and may have the value of 1 (i.e.,Primary Device) as the TargetDevice element value. (L77010)

The component element for the Presentable Audio Component (5.1 channels)may have the value of 2 (i.e., Audio) as the ComponentType elementvalue, may have the value of 6 (i.e., Completely Main) as theComponentRole element value, may have KOR (i.e., Korean) as the Languageelement value, may have the value of 11 (i.e., 5.1 channels) as theDeviceCapability element value, and may have the value of 1 (i.e.,Primary Device) as the TargetDevice element value. (L77010)

The receiver (Device) according to one embodiment may acquire theDeviceCapability element value, may determine whether the correspondingfunction can be supported, and may provide the user with the Capabilityinformation.

As can be seen from the upper right part of FIG. 77, a screen imagedisplayed on the device configured to support HD and 5.1 channels isshown as shown in FIG. 77. In this case, the embodiment of the presentinvention can display specific information indicating that thecorresponding device can support HD and 5.1 channels on the screen.(L77020)

Although the lower right part of FIG. 77 can support the HD function, itshould be noted that a screen image of the device not supporting 5.1channels may also be shown in FIG. 77 as necessary. In this case,according to one embodiment, when the receiver not supporting 5.1channels obtains the Capability information, the non-supported 5.1channels audio information may be grayed out such that thegrayout-processed result may be displayed on the screen. (L77030)

FIG. 78 illustrates an XML schema of a Component element when aPresentable Video component (UHD) and Presentable ENG audio componentare transmitted as broadcast signals and a Presentable SPA audiocomponent is transmitted as a broadband signal.

Referring to FIG. 78, according to one embodiment of the presentinvention, if the Presentable Video component (UHD) and the PresentableENG audio component are transmitted through broadcast, and if thePresentable SPA audio component is transmitted through broadband, theannouncement function may use three Components as the sub-element of thePrivateExt element contained in the Content fragment. (L78010)

The component element for the Presentable Video component (UHD) may havethe value of 1 (i.e., Video) as the ComponentType element value, mayhave the value of 1 (i.e., Primary Video) as the ComponentRole elementvalue, may have the value of 4 (i.e., UHD) as the DeviceCapabilityelement value, and may have the value of 1 (i.e., Primary Device) as theTargetDevice element value. (L78010)

The component element for the Presentable ENG audio component (throughBroadcast) may have the value of 2 (i.e., Audio) as the ComponentTypeelement value, may have the value of 6 (i.e., Completely Main) as theComponentRole element value, may have ENG (English) as the Languageelement value, and may have the value of 1 (i.e., Primary Device) as theTargetDevice element value. (L78010)

The component element for the Presentable SPA audio component (throughBroadband) may have the value of 2 (i.e., Audio) as the ComponentTypeelement value, may have the value of 6 (i.e., Completely Main) as theComponentRole element value, may have SPA (Spanish) as the Languageelement value, and may have the value of 1 (indicating that thecomponent is transmitted through broadcast) as the DeviceCapabilityelement value, and may have the value of 1 (i.e., Primary Device) as theTargetDevice element value. (L78010)

The receiver (Device) according to one embodiment obtains theDeviceCapability element value, determines whether the correspondingfunction can be supported, and provides the user with the Capabilityinformation.

Assuming that the right part of FIG. 78 does not support broadbandconnection, or assuming that the right part of FIG. 78 is in anon-connection state whereas it can support broadband connection, it maybe possible to display the screen displayed on the receiver (Device).(L78020)

The receiver according to one embodiment of the present invention mayrecognize that the corresponding component is transmitted throughbroadband, when the DeviceCapability element is set to 1. In this case,the device not supporting broadband connection or the other device beingin a non-connection whereas it can support broadband connection canperform grayout processing of the broadband transmission component, andcan display the processed result on the screen. In this case, the SPAaudio information is grayed out and then displayed on the screen.(78020)

FIG. 79 illustrates an XML schema of a Component element when aPresentable Video Component (UHD/Wide Color Gamut) and a PresentableAudio Component (5.1 channels) are transmitted.

Referring to FIG. 79, according to one embodiment of the presentinvention, when the Presentable Video Component (UHD/Wide Color Gamut)and the Presentable Audio Component (5.1 channels) are transmitted, theannouncement function may use two Components as the sub-element of thePrivateExt element contained in the Content fragment. (L79010)

The component element for the Presentable Video Component (UHD/WideColor Gamut) may have the value of 1 (Video) as the ComponentTypeelement value, may have the values of 4 (UHD) and 8 (WCG) as theDeviceCapability element values, and may have the value of 1 (i.e.,Primary Video) as the TargetDevice element value. (L79010)

The component element for the Presentable Audio Component (5.1 channels)may have the value of 2 (i.e., Audio) as the ComponentType elementvalue, may have the value of 6 (i.e., Completely Main) as theComponentRole element value, may have KOR (i.e., Korean) as the Languageelement value, may have the value of 11 (i.e., 5.1 channels) as theDeviceCapability element value, and may have the value of 1 (i.e.,Primary Device) as the TargetDevice element value. (L79010)

The receiver (Device) according to one embodiment may acquire theDeviceCapability element value, may determine whether the correspondingfunction can be supported, and may provide the user with the Capabilityinformation.

As can be seen from the upper right part of FIG. 79, a screen imagedisplayed on the device configured to support UHD, WCG (Wide ColorGamut) and 5.1 channels is shown as shown in FIG. 79. In this case, theembodiment of the present invention can display specific informationindicating that the corresponding device can support UHD, WCG and 5.1channels on the screen. (L79020)

Although the lower right part of FIG. 79 can support UHD and 5.1channels, it should be noted that a screen image of the device notsupporting WCG may also be shown in FIG. 79 as necessary. In this case,according to one embodiment, when the receiver not supporting 5.1channels obtains the Capability information, the non-supported WCGinformation may be grayed out such that the grayout-processed result maybe displayed on the screen. (L79030)

FIG. 80 illustrates a component element according to another embodimentof the present invention.

Referring to FIG. 80, the component element may be a root element of thecomponent sub-element. The component element may start from the E3level. Since the component element describes detailed content of thecomponent, as many elements as the number of components may bedescribed. In association with some components, the component elementmay also be omitted as necessary. Therefore, the component element mayhave cardinality of 0 . . . N. The component element may include theComponentType attribute, the ComponentRole element, the Languageelement, and/or the EssentialCapabilities element.

The ComponentType field may include attribute information indicating thecomponent type. That is, the ComponentType field indicates the attributeindicating the component type. The ComponentType field is an essentialelement indicating the component type, such that the ComponentType fieldmay be set to 1. The ComponentTypinfield may identify that the componentcorresponds to Presentable Video, Presentable Audio, Presentable CC(closed caption) and/or Presentable App according to the value thereof.

The message shown in FIG. 80 may include one or more fields therein.Each field may include unique meaning or information. Type informationmay be allocated to each field. The type information may have the valueof ‘E’, ‘A’, ‘E1’, ‘E2’, or ‘E[n]’. The E value may indicate that thecorresponding field relates to the element. The A value may indicatethat the corresponding field relates to the attribute information. TheE1 value may indicate that the corresponding field relates to the subelement. The sub-element may correspond to a lower element defined inthe element. The E2 value may represent a lower sub-element of thesub-element. That is, the E[n] element may represent the [n1]-th lowerelement.

FIG. 81 illustrates a ComponentRol element according to an embodiment ofthe present invention.

Referring to FIG. 81, the ComponentRole element is an element todescribe the role of the component. The ComponentRole element is definedas a lower element of the component. The ComponentRole element may startfrom the E3 level. The ComponentRole element may have a String value.The ComponentRole element value may be designated as the arbitrary validstring value decided by a broadcast station manufacturing theAnnouncement Data. The ComponentRole element value may be an extensiblestring value, such that it can describe all kinds of the CapabilityStrings without difficulty. The target device (e.g., receiver) maydisplay information available for the end user (e.g., a TV viewer) usingthe ComponentRole element value.

In association with the component, the ComponentRole element may includespecific information providing letter-shaped information capable ofbeing recognized by the TV viewer.

The ComponentRole element may represent various kinds of components. Forexample, in association with the presentable video component, theComponentRole element may include “Primary video”, “Alternative cameraview”, “Other alternative video component”, “Sign language inset”,and/or “Follow subject video”.

The ComponentRole element may represent various kinds of components. Forexample, in association with the presentable audio component, theComponentRole element may include “Complete main”, “Music”, “Dialogue”,“Effects”, “Visually impaired”, “Hearing impaired” and/or “Commentary”.

The ComponentRole element may represent various kinds of components. Forexample, in association with the presentable CC component, theComponentRole element may include “Normal” and/or “Easy reader”.

The ComponentRole element may represent various kinds of components. Forexample, in association with the Presentable App (application)component, the ComponentRole element may include “On Demand”,“Startover”, and/or “CompanionScreen”.

FIG. 82 illustrates an XML-formatted component element according toanother embodiment of the present invention.

Referring to FIG. 82, the component element according to one embodimentmay perform signaling of each component when the component is composedof various kinds of media, such that a viewer-desired component or areceiver-desired component can be identified in advance in the receptionend. In addition, the role of the component can be provided in the formof letters, such that the component desired by the viewer who consumesthe corresponding information may be easily recognized or selected.

The component element according to one embodiment may be extended andthen contained in the Service Guide Content Fragment pre-defined in OMABCAST as necessary.

FIG. 83 is a conceptual diagram illustrating a Component elementaccording to another embodiment of the present invention.

Referring to FIG. 83, the component element is a root element of theComponent Sub-element. The component element may start from the E2level. Since the component element describes detailed content of eachcomponent, as many elements as the number of components may bedescribed. In association with some components, the component elementmay also be omitted as necessary. Therefore, the component element mayhave cardinality of 0 . . . N. The component element may include thePresentable VideoComponent element, the PresentableAudioComponentelement, the PresentableCCComponent element, and/or thePresentableAppComponent element.

The PresentableVideoComponent element may be an element to describe thePresentable Video Component. The Presentable VideoComponent element is alower element of the component element, and may start from the E3 level.The Presentable VideoComponent element may have a string value, and maydescribe the role of the video component. In association with thecomponent, the Presentable VideoComponent element may include specificinformation to provide letter-shaped description capable of beingrecognized by the TV viewer. The role of the component capable of beingrepresented by the Presentable VideoComponent element may include“Primary video”, “Alternative camera view”, “Other alternative videocomponent”, “Sign language inset”, and/or “Follow subject video”.

The PresentableAudioComponent element may be an element to describe thePresentable Audio Component. The PresentableAudioComponent elementacting as a lower element of the component element may start from the E3level. The PresentableAudioComponent element may have the string value,and may describe the role of the audio component. In association withthe component, the PresentableAudioComponent element may providespecific information to provide letter-shaped description capable ofbeing recognized by the TV viewer. The role of the component capable ofbeing represented by the PresentableAudioComponent element may include“Complete main”, “Music”, “Dialog”, “Effects”, “Visually impaired”,“Hearing impaired” and/or “Commentary”.

FIG. 84 illustrates a PresentableCCComponent element and aPresentableAppComponent element according to another embodiment of thepresent invention.

Referring to FIG. 84, the element shown in FIG. 84 may be contained inthe above-mentioned component element shown in FIG. 83.

The PresentableCCComponent element may be an element to describe thePresentable CC Component. The PresentableCCComponent element acting as alower element of the component element may start from the E3 level. ThePresentableCCComponent element may have the string value, and maydescribe the role of the CC component. In association with thecomponent, the PresentableCCComponent element may include specificinformation to provide letter-shaped description capable of beingrecognized by the viewer. The component capable of being denoted by thePresentableCCComponent element may include “Normal” and/or “Easyreader”.

The PresentableAppComponent element may be an element to describe thePresentable App Component. The PresentableAppComponent element acting asa lower element of the component element may start from the E3 level.The PresentableAppComponent element may have the string value, and maydescribe the role of the App Component. In association with thecomponent, the PresentableAppComponent element may include specificinformation to provide letter-shaped description capable of beingrecognized by the TV viewer. The component capable of being denoted bythe PresentableAppComponent element may include “On Demand”,“Startover”, and/or “CompanionScreen”.

If the component element is constructed according to the embodiment ofthe present invention, the number of repeated use times of theconstituent elements and/or attribute values needed to construct the newcomponent fragments can be greatly reduced, and announcement informationcan be effectively and intuitively provided to the End User.

FIG. 85 illustrates an XML-formatted component element according toanother embodiment of the present invention.

Referring to FIG. 85, if the component element according to anotherembodiment of the present invention is comprised of various kinds ofmedia, the component element may perform signaling of each componenttype, such that a viewer-desired component or a receiver-desiredcomponent can be identified in advance in the reception end. Inaddition, the role of the component can be provided in the form ofletters, such that the component desired by the viewer who consumes thecorresponding information may be easily recognized or selected. Inaddition, the role of the component may be provided in the form ofletters, such that the component desired by the viewer who consumes thecorresponding information can be readily recognized and selected. Inaddition, according to another embodiment of the present invention, thecomponent element may be constructed in different ways according tocomponent types, and may describe the role of each component using thestring, resulting in acquisition of the extensibility.

The component element according to one embodiment may also be extendedin the Service Guide Content Fragment pre-defined in OMA BCAST asnecessary.

FIG. 86 illustrates Essential Capabilities elements according to anembodiment of the present invention.

Referring to FIG. 86, according to one embodiment of the presentinvention, the component element may include the Capability item. TheCapability item may correspond to specific information indicating thereceiver throughput needed when the receiver can properly decode thecorresponding component. The Capability item may be comprised of thecombination of the Capability code and the String. The embodiment of thepresent invention may provide a method for additionally defining a newvalue in the Capability code and Capability category.

Referring to FIG. 86, the Capability item may be defined as a lowerelement of the component element. The Capability item may include theEssentialCapabilities element, the CapabilityCodes element, theCapabilityString element, and/or the Category attribute information.

The EssentialCapabilities element may describe the capability requiredfor the meaningful presentation of the service (Media, BroadcastService). The EssentialCapabilities element may include theCapabilityCodes element and/or the CapablityString element. TheEssentialCapabilities element may be defined as a lower element of thecomponent element, and may start from the E3 level.

The CapabilityCodes element may have the value regarding the codeidentifying the capability category. The CapabilityCodes element mayindicate one or more capabilities.

The Capability String element may include a string to describe thecapability. The CapabilityString element may include information todescribe the capability using letters. The CapabilityString element mayinclude Category attribute information.

The Category attribute information may indicate category of thecapability described by the Capability String element.

FIG. 87 illustrates the meaning of Capability in response to aCapabilityCode element value according to an embodiment of the presentinvention.

As shown in FIG. 87, the CapabilityCode element may have differentmeanings according to different values thereof.

In accordance with the embodiment, a new value is defined in theDownload Protocols item, and the capability denoted by the correspondingvalue may be established to correspond to “IP via Broadband”. That is,data may be received through Broadband IP in the next generationbroadcast system, and the received result may be added, as onecapability type, to the Download Protocol corresponding to IP viaBroadband.

In accordance with the embodiment of the present invention, theCapabilityCode element may identify the Rendering Capability. Inaccordance with the CapabilityCode element value, the RenderingCapability requisite for the receiver may be signaled to use thecomponent. The Rendering Capability denoted by the CapabilityCodeelement may indicate which video, audio, application, and/or CC can berendered by the receiver.

FIG. 88 illustrates a Capability Category dependent upon a Categoryattribute information value.

Referring to FIG. 88, the value of the Category attribute informationmay be additionally defined in a manner that the capability is containedin the Rendering Capability category. For example, assuming that theCategory attribute information is set to 0x06, this means that thecapability is contained in the Rendering Capability category.

FIG. 89 is a conceptual diagram illustrating a method for providing aPPV (Pay Per View) program to each component according to an embodimentof the present invention.

Referring to FIG. 89, the PayPerView service per component may beprovided. That is, according to one embodiment of the present invention,within one service or content, a specific component can be provided tothe user through a pay per view. For example, according to theembodiment of the present invention, the component is defined in theannouncement, such that the PayPerView service can be provided accordingto the component.

For this purpose, attribute and/or element information regarding thecomponent element may be described in the content and then transmitted.Each component may have pay-for-use information. The broadcast program(media, broadcast service, or broadcast content) may be provided free ofcharge, and the broadcast station may impose a predetermined charge toeach component according to the quality and amount of additionalinformation of each component of the broadcast program. For example, inorder to allow the TV viewer to view the UHD video component but not thefree-of-charge HD video component, the broadcast station may provide theTV viewer with the UHD video component through Pay Per View.Alternatively, the broadcast station may impose a predetermined chargeto each audio component for stereoscopic sound of the Audio component.Alternatively, the broadcast station may impose a predetermined chargeto a component requisite for the voting application configured toactivate the voting broadcast program, such that the TV viewer whodesires to participate in the voting must pay for the requisitecomponent. The above-mentioned scheme is referred to as a Pay Per Viewscheme implemented by ESG transmitted per component.

In order to establish the PPV function per component, the componentelement may include PPV related information in association with eachcomponent. Alternatively, the ComponentRole element may include PPVrelated information in association with each component role. PPV relatedinformation may include ID information for identifying whether PPV isapplied to the component or the component role; PPV payment information;PPV cost information; authentication related information aftercompletion of PPV payment; and/or duration information through which thecorresponding component can be validly used after completion of PPVpayment.

Referring to FIG. 89, according to the embodiment of the presentinvention, it can be recognized that PPV elements are present in thebroadcast program through the ESG (Electronic Service Guide). Thereceiver may display the item of the PPV components through ESG. If theTV viewer selects a broadcast program having PPV elements, the receivermay indicate the presence of one or more PPV elements in thecorresponding program, may display a User Interface (UI) for queryingthe TV viewer whether to view the PPV element, and may thus receive theselection command from the TV viewer. This embodiment illustrates anexemplary case in which not only basic images of the broadcast programbut also additional images are present. If the TV viewer pays for thePPV Video Component corresponding to the Alternative View, the TV viewercan view the Alternative View images. In this case, the above-mentionedcontrol unit may construct a broadcast program schedule using the PPVrelated information. The broadcast program schedule includes a specificmark indicating whether PPV is applied to a specific component. Theabove-mentioned display unit may display the broadcast program schedulethereon.

The TV viewer may select the Alternative View images, and view the sameat a later time as necessary. In this case, if a current display imagestops displaying, the Alternative View images may be displayed.Alternatively, the Alternative View images may be displayed at aspecific time desired by the TV viewer. Alternatively, the TV viewer mayview in real time not only basic images provided from the main devicebut also the Alternative View images using the Companion Device.

FIG. 90 is a flowchart illustrating a method for providing media to eachcomponent of a broadcast program according to an embodiment of thepresent invention.

Referring to FIG. 90, the receiver may receive ESG (Electronic ServiceGuide) data through broadcast signals (J590010). The ESG data mayinclude the above-mentioned elements, the Service fragment, the Contentfragment, the Schedule fragment, and/or the Component Fragment.

The receiver may parse the Service fragment, and may thus generate thelist of broadcast stations to be displayed on the channel list(J590020).

The receiver may parse the Content fragment, and may thus provide thelist of broadcast programs per broadcast station (J590030).

The receiver may parse the schedule fragment, and may thus generate aschedule of the broadcast programs per broadcast station (J590040).

The receiver may receive a command for displaying a broadcast programschedule from the TV viewer or the user (J590050).

The receiver may determine whether the role of the component containedin the broadcast service or the broadcast program is displayed on theESG (J590060).

If the role of the component contained in the broadcast service or thebroadcast program is displayed on the ESG, the receiver may displaydetailed information of each program contained in the broadcast programsschedule (J590070). The receiver may obtain information regarding thecomponent role from the above-mentioned component element and thesub-element thereof.

The receiver may receive a selection command of a specific program or areserved viewing command of the specific program from the TV viewer orthe user (J590080).

The receiver may enter (or decode) the broadcast programs elected by theTV viewer or the user (J590090).

The receiver may display the Video, Audio, CC, and/or App Components onthe display screen according to the role of each component contained inthe broadcast program (J590100). The receiver may receive the commandfor selecting any one of the Video, Audio, CC, and/or App Componentsfrom the TV viewer or the user. In this case, assuming that the PPVpolicy for each component is present, the PPV program can be processedas described above. A specific message indicating the presence orabsence of the PPV policy for each component may be displayed on theESG.

The TV viewer or the user may view the media displayed by the receiver(JS90100).

In the meantime, if the role of component contained in the broadcastservice or the broadcast program is not displayed on the ESG, thereceiver may display time information of the program and/or the name ofthe program contained in the broadcast program schedule (JS90120).

The receiver may receive a selection command of a specific programcontained in the broadcast program schedule or the reserved viewingcommand of the specific program from the TV viewer or the user(JS90130).

The receiver may enter (decode) the broadcast program selected by the TVviewer/user (JS90140).

In the meantime, if the TV viewer or the user who views the broadcastprogram inputs a command for displaying the broadcast program schedule,the receiver may perform the procedures starting from the step JS90050.

FIG. 91 exemplarily illustrates screen images through which media issupplied to each component of a broadcast program according to anembodiment of the present invention.

Referring to the step (L91010) shown in FIG. 91, in association with theprogram (G) manufactured by the broadcast station (CNTV) displayed onthe ESG, the role of each component is shown in FIG. 91. If necessary,the role of each component may not be shown in FIG. 91. For example, ifthe component role is displayed on the ESG, the ESG may indicate thatthe components capable of providing the ‘Alternative View’, ‘FollowSubject’ and ‘Sign Language’ elements are present in relation to the Gprogram.

Referring to the step (L91020), if the G program is displayed, thereceiver may display not only ‘Sign language’ but also ‘follow subjectvideo’ at the same time, or may display thumbnail images related tothese components. In this case, ‘Sign language’ may correspond to signlanguage, and ‘follow subject video’ may correspond to images related toa current program.

Referring to the step (L91030), assuming that the TV viewer or the userselects the ‘Alternative View’ function in relation to the G program,not only basic images of the current program but also the remainingimages other than the basic images may be displayed.

FIG. 92 exemplarily illustrates screen images through which the role ofa video component is displayed on ESG according to an embodiment of thepresent invention.

The receiver receives a request of the broadcast program schedule fromthe TV viewer, and displays the requested broadcast program schedule.Information regarding the broadcast program located after the currenttime may be displayed on the broadcast program schedule. Specificinformation indicating that the component corresponding to a specificrole related to a specific program may be displayed on the ESG. Forexample, the sing language content may be provided to the program (B).Therefore, the TV viewer who desires to view the sign language contentmay select a broadcast program in which the letters ‘sign language’ aredisplayed, may perform channel switching of the corresponding program,or may perform reserved viewing of the corresponding program. Thereceiver may provide the TV viewer with queries indicating whether toview the corresponding program when a current time reaches the starttime of the reserved broadcast program, and then display thecorresponding program.

FIG. 93 exemplarily illustrates screen images through which the role ofa video component is displayed on ESG according to another embodiment ofthe present invention.

Referring to FIG. 93, the receiver may receive a request for thebroadcast program schedule from the TV viewer, and may display thebroadcast program schedule. Information regarding the broadcast programlocated after the current time may be displayed on the broadcast programschedule. Specific information indicating that the componentcorresponding to a specific role related to a specific program may bedisplayed on the ESG. For example, the broadcast program schedule mayindicate the presence of the Alternative View element in the G program.If the user selects the G program, the receiver may provide the TVviewer with queries whether to view the corresponding program. If thereceiver receives an indication command of the Alternative View elementfrom the TV viewer, the receiver may replace the current image withthose of the ‘Alternative View’ element, and then display the replacedresult. Alternatively, the receiver transmits the ‘Alternative View’related information to the companion device, and thus allows thecompanion device to display the Alternative View images.

FIG. 94 exemplarily illustrates screen images through which the role ofa video component is displayed on ESG according to another embodiment ofthe present invention.

Referring to FIG. 94, the receiver may receive a request for thebroadcast program schedule from the TV viewer, and may display thebroadcast program schedule. Information regarding the broadcast programlocated after the current time may be displayed on the broadcast programschedule. Specific information indicating that the componentcorresponding to a specific role related to a specific program may bedisplayed on the ESG. For example, the broadcast program schedule mayindicate the presence of the Follow Subject Video element in the program(I). If the user selects the I program, the receiver may provide the TVviewer with queries whether to confirm the Follow Subject Video element.If the receiver receives an indication command of the Follow SubjectVideo element from the TV viewer, the receiver may replace the currentimage with those of the Follow Subject Video element, and then displaythe replaced result. Alternatively, the receiver transmits the ‘FollowSubject Video’ related information to the companion device, and thusallows the companion device to display the Follow Subject Video images.

FIG. 95 exemplarily illustrates screen images through which the role ofan audio component is displayed on ESG according to an embodiment of thepresent invention.

Referring to FIG. 95, the receiver may receive a request for thebroadcast program schedule from the TV viewer, and may display thebroadcast program schedule. Information regarding the broadcast programlocated after the current time may be displayed on the broadcast programschedule. Specific information indicating that the componentcorresponding to a specific role related to a specific program may bedisplayed on the ESG. For example, the broadcast program schedule mayindicate the presence of the Music component element in the program (I).The Music component may correspond to a component configured to providehigh-quality sound audio data for the corresponding program. As aresult, the TV viewer who desires to receive high-quality sound audiodata selects the I program, and can thus simultaneously consume thecorresponding program and the Music component.

FIG. 96 exemplarily illustrates screen images through which the role ofan audio component is displayed on ESG according to another embodimentof the present invention.

Referring to FIG. 96, the receiver may receive a request for thebroadcast program schedule from the TV viewer, and may display thebroadcast program schedule. Information regarding the broadcast programlocated after the current time may be displayed on the broadcast programschedule. Specific information indicating that the componentcorresponding to a specific role related to a specific program may bedisplayed on the ESG. For example, the broadcast program schedule mayindicate the presence of the Dialogue component element in the Gprogram. The Dialogue component may correspond to an additionalcomponent related to speech (or lines) of a specific actor or actress ofthe corresponding program. The TV viewer may select the G programproviding the Dialogue component, may reproduce the dialogue of theactor or actress of the corresponding program through a separatespeaker, and may consume the corresponding content. If the Dialoguecomponent is separately provided, the receiver may also separatelyadjust the level of the Dialogue component.

FIG. 97 exemplarily illustrates screen images through which the role ofan audio component is displayed on ESG according to another embodimentof the present invention.

Referring to FIG. 97, the receiver may receive a request for thebroadcast program schedule from the TV viewer, and may display thebroadcast program schedule. Information regarding the broadcast programlocated after the current time may be displayed on the broadcast programschedule. Specific information indicating that the componentcorresponding to a specific role related to a specific program may bedisplayed on the ESG. For example, the broadcast program schedule mayindicate the presence of the Visually Impaired component element in theD program. The Visually Impaired component may correspond to thecomponent configured to audibly provide visual content provided from thecorresponding program. The Visually Impaired component may be used toprovide the visually handicapped person (blind) with audible descriptionrelated to the corresponding program. The TV viewer may select theprogram D configured to provide the Visually Impaired component, andthus consume the content corresponding to the Visually Impairedcomponent. In this case, the receiver may reproduce the VisuallyImpaired component through the main device, may transmit the VisuallyImpaired component to the companion device, and may thus allow thecompanion device to reproduce the corresponding component.

FIG. 98 illustrates an exemplary case in which the role of a ClosedCaption (CC) component is displayed on ESG according to an embodiment ofthe present invention.

Referring to FIG. 98, the receiver may receive a request for thebroadcast program schedule from the TV viewer, and may display thebroadcast program schedule. Information regarding the broadcast programlocated after the current time may be displayed on the broadcast programschedule. Specific information indicating that the componentcorresponding to a specific role related to a specific program may bedisplayed on the ESG. For example, the broadcast program schedule mayindicate the presence of the Easy Reader component element in the Dprogram. The Easy Reader component may correspond to the componentconfigured to provide caption or subtitles of the content of thecorresponding broadcast program. The caption or subtitles may beconstructed in one or more languages. The TV viewer may select the Dprogram configured to provide the Easy Reader component, and may consumethe content corresponding to the Easy Reader component. In this case,the receiver may reproduce the Easy Reader component through the maindevice, and may transmit the Easy Reader component to the companiondevice, such that the companion device can reproduce the correspondingcomponent.

FIG. 99 is a flowchart illustrating a method for receiving andprocessing broadcast signals according to an embodiment of the presentinvention.

The broadcast signal transmission method according to an embodiment ofthe present invention may include generating service guide informationincluding access information of a broadcast service and content data(SL99010), encoding the generated service guide information and contentdata (SL99020), and/or transmitting the encoded service guideinformation and content data (SL99030). The service guide informationmay include a service fragment indicating information about thebroadcast service. In this case, the service guide information mayindicate a service guide and the service fragment may indicate a Servicefragment.

According to another embodiment of the present invention, the servicefragment may include service type information indicating the type of thebroadcast service. In this case, the type of the broadcast serviceindicated by the service type information may include a linear service(Linear Service) that provides broadcast schedule information as well,an application based service (Appbased Service), and/or a companionscreen service (CompanionScreen Service) using a companion device. Inthis case, the service type information may indicate informationincluded in a ServiceType element. A detailed description thereof hasbeen given with reference to FIGS. 27, 28, 29, and 30.

According to another embodiment of the present invention, the serviceguide information may include a component fragment indicatinginformation about a component included in the broadcast service. Thecomponent fragment may include information that identifies the componentfragment, component type information indicating the type of thecomponent, and/or component role information indicating the role of thecomponent. In this case, the component fragment may indicate a Componentfragment. The information that identifies the component fragment mayindicate information included in an id attribute. The component typeinformation may indicate information included in a ComponentType elementand the component role information may indicate information included ina ComponentRole element. A detailed description thereof has been givenwith reference to FIGS. 31, 32, 60, 61, and 62.

According to another embodiment of the present invention, the type ofthe component indicated by the component type information may include acontinuous component (Continuous component) indicating a componentrepresented in one continuous stream, an elementary component(Elementary component) indicating an independently encoded component, acomposite component (Composite component) indicating a component thatcan be combined for one presentation, and/or a pick-one component(PickOne component) indicating a component selected for onepresentation. A detailed description thereof has been given withreference to FIG. 63.

According to another embodiment of the present invention, the componentrole information may indicate that the component performs the role of abase layer for scalable video encoding, an enhancement layer forscalable video encoding, a left-eye image of 3D video, a right-eye imageof 3D video, depth information of 3D video, music audio, dialog audio,and/or caption for children. In this case, the base layer for scalablevideo encoding may indicate a Base layer for scalable video encoding,the enhancement layer for scalable video encoding may indicate anEnhancement layer for scalable video encoding with level, the left-eyeimage of 3D video may indicate a 3D video left view, the right-eye imageof 3D video may indicate a 3D video right view, the depth information of3D video may indicate 3D video depth information, the music audio mayindicate Music, the dialog audio may indicate Dialog, and the captionfor children may indicate Easy reader. A detailed description thereofwill be given with reference to FIG. 64.

FIG. 100 is a diagram illustrating a broadcast signal receptionapparatus according to an embodiment of the present invention.

A broadcast signal reception apparatus L100030 according to anembodiment of the present invention may include a receiver L100010and/or a decoder L100020.

The receiver may receive service guide information including accessinformation of a broadcast service and/or content data. The serviceguide information may include a service fragment indicating informationabout the broadcast service.

The decoder may decode the received service guide information and/orcontent data.

According to another embodiment of the present invention, the servicefragment may include service type information indicating the type of thebroadcast service. In this case, the type of the broadcast serviceindicated by the service type information may include a linear service(Linear Service) that provides broadcast schedule information, anapplication based service (Appbased Service), and/or a companion screenservice (CompanionScreen Service) using a companion device. In thiscase, the service type information may indicate information included ina ServiceType element. A detailed description thereof has been givenwith reference to FIGS. 27, 28, 29, and 30.

According to another embodiment of the present invention, the serviceguide information may include a component fragment indicatinginformation about a component included in the broadcast service. Thecomponent fragment may include information that identifies the componentfragment, component type information indicating the type of thecomponent, and/or component role information indicating the role of thecomponent. In this case, the component fragment may indicate a Componentfragment. The information that identifies the component fragment mayindicate information included in an id attribute. The component typeinformation may indicate information included in a ComponentType elementand the component role information may indicate information included ina ComponentRole element. A detailed description thereof has been givenwith reference to FIGS. 31, 32, 60, 61, and 62.

According to another embodiment of the present invention, the type ofthe component indicated by the component type information may include acontinuous component (Continuous component) indicating a componentrepresented in one continuous stream, an elementary component(Elementary component) indicating an independently encoded component, acomposite component (Composite component) indicating a component thatcan be combined for one presentation, and/or a pick-one component(PickOne component) indicating a component selected for onepresentation. A detailed description thereof has been given withreference to FIG. 63.

According to another embodiment of the present invention, the componentrole information may indicate that the component performs the role of abase layer for scalable video encoding, an enhancement layer forscalable video encoding, a left-eye image of 3D video, a right-eye imageof 3D video, depth information of 3D video, music audio, dialog audio,and/or caption for children. In this case, the base layer for scalablevideo encoding may indicate a Base layer for scalable video encoding,the enhancement layer for scalable video encoding may indicate anEnhancement layer for scalable video encoding with level, the left-eyeimage of 3D video may indicate a 3D video left view, the right-eye imageof 3D video may indicate a 3D video right view, the depth information of3D video may indicate 3D video depth information, the music audio mayindicate Music, the dialog audio may indicate Dialog, and the captionfor children may indicate Easy reader. A detailed description thereofwill be given with reference to FIG. 64.

FIG. 101 is a diagram illustrating a broadcast signal transmissionapparatus according to an embodiment of the present invention.

A broadcast signal transmission apparatus L101040 according to anembodiment of the present invention may include a generator L101010, anencoder L101020, and/or a transmitter L101030.

The generator may generate service guide information including accessinformation of a broadcast service and content data. The service guideinformation may include a service fragment indicating information aboutthe broadcast service.

The encoder may encode the generated service guide information andcontent data.

The transmitter may transmit the encoded service guide information andcontent data.

According to another embodiment of the present invention, the servicefragment may include service type information indicating the type of thebroadcast service. In this case, the type of the broadcast serviceindicated by the service type information may include a linear service(Linear Service) that provides broadcast schedule information, anapplication based service (Appbased Service), and/or a companion screenservice (CompanionScreen Service) using a companion device. In thiscase, the service type information may indicate information included ina ServiceType element. A detailed description thereof has been givenwith reference to FIGS. 27, 28, 29, and 30.

FIG. 102 is a diagram illustrating a broadcast signal reception methodaccording to an embodiment of the present invention.

The broadcast signal reception method according to an embodiment of thepresent invention may include receiving service guide informationincluding access information of a broadcast service and content data(SL102010) and/or decoding the received service guide information andcontent data (SL102020). The service guide information may include aservice fragment indicating information about the broadcast service.

According to another embodiment of the present invention, the servicefragment may include service type information indicating the type of thebroadcast service. In this case, the type of the broadcast serviceindicated by the service type information may include a linear service(Linear Service) that provides broadcast schedule information, anapplication based service (Appbased Service), and/or a companion screenservice (CompanionScreen Service) using a companion device. In thiscase, the service type information may indicate information included ina ServiceType element. A detailed description thereof has been givenwith reference to FIGS. 27, 28, 29, and 30.

According to another embodiment of the present invention, the serviceguide information may include a component fragment indicatinginformation about a component included in the broadcast service. Thecomponent fragment may include information that identifies the componentfragment, component type information indicating the type of thecomponent, and/or component role information indicating the role of thecomponent. In this case, the component fragment may indicate a Componentfragment. The information that identifies the component fragment mayindicate information included in an id attribute. The component typeinformation may indicate information included in a ComponentType elementand the component role information may indicate information included ina ComponentRole element. A detailed description thereof has been givenwith reference to FIGS. 31, 32, 60, 61, and 62.

The module or unit may be one or more processors designed to execute aseries of execution steps stored in the memory (or the storage unit).Each step described in the above-mentioned embodiments may beimplemented by hardware and/or processors. Each module, each block,and/or each unit described in the above-mentioned embodiments may berealized by hardware or processor. In addition, the above-mentionedmethods of the present invention may be realized by codes written inrecoding media configured to be read by a processor so that the codescan be read by the processor supplied from the apparatus.

Although the description of the present invention is explained withreference to each of the accompanying drawings for clarity, it ispossible to design new embodiment(s) by merging the embodiments shown inthe accompanying drawings with each other. And, if a recording mediumreadable by a computer, in which programs for executing the embodimentsmentioned in the foregoing description are recorded, is designed innecessity of those skilled in the art, it may belong to the scope of theappended claims and their equivalents.

An apparatus and method according to the present invention may benon-limited by the configurations and methods of the embodimentsmentioned in the foregoing description. And, the embodiments mentionedin the foregoing description can be configured in a manner of beingselectively combined with one another entirely or in part to enablevarious modifications.

In addition, a method according to the present invention can beimplemented with processor-readable codes in a processor-readablerecording medium provided to a network device. The processor-readablemedium may include all kinds of recording devices capable of storingdata readable by a processor. The processor-readable medium may includeone of ROM, RAM, CD-ROM, magnetic tapes, floppy discs, optical datastorage devices, and the like for example and also include such acarrier-wave type implementation as a transmission via Internet.Furthermore, as the processor-readable recording medium is distributedto a computer system connected via network, processor-readable codes canbe saved and executed according to a distributive system.

It will be appreciated by those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

Both the product invention and the process invention are described inthe specification and the description of both inventions may besupplementarily applied as needed.

It will be appreciated by those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both of the apparatus and method inventions may becomplementarily applicable to each other.

Various embodiments have been described in the best mode for carryingout the invention.

The embodiments of the present invention is available in a series ofbroadcast signal provision fields.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

1-8. (canceled)
 9. A device for processing a broadcast signal, the device comprising: a receiver to receive the broadcast signal including physical layer signaling data, signaling data, content data and service guide information; a decoder to obtain the service guide information from the broadcast signal, the service guide information including a service fragment including information about a broadcast service and a content fragment including information about content data of the broadcast service, the content fragment including capability information required for displaying the content data so that the device generates user selectable information based on the capability information, the user selectable information including first sub-user selectable information representing one or more capabilities which are supported by the device, and second sub-user selectable capability information representing one or more capabilities which are not supported by the device based on the capability information; and a controller to control a display screen to display the user selectable information and the content data.
 10. The device of claim 9, wherein the display screen is further configured to display the first sub-user selectable information on a first portion of the display screen, to display the second sub-user selectable information on a second portion of the display screen, and to display the content data on a third portion of the display screen.
 11. The device of claim 10, wherein the controller is further configured to control the display screen to adjust at least one of color and brightness of the second portion.
 12. The device of claim 10, wherein the first portion is distinct from the second portion and the third portion, and the second portion is distinct from the third portion.
 13. The device of claim 10, wherein a size of the third portion is greater than a size of the first portion and a size of the second portion.
 14. The device of claim 9, wherein the capability information further includes one or more video formats of video components of the content data, and one or more audio formats of audio components of the content data.
 15. The device of claim 9, wherein the device is further configured to detect a user input signal to select at least one capability represented by the first sub-user selectable information, in response to detecting the user input signal, the controller controlling the display screen to display the content data in accordance with a selection of the at least one capability.
 16. A method for processing a broadcast signal, the method comprising: receiving the broadcast signal including physical layer signaling data, signaling data, content data and service guide information; obtaining the service guide information from the broadcast signal, the service guide information including a service fragment including information about a broadcast service and a content fragment including information about content data of the broadcast service, the content fragment including capability information required for displaying the content data so that the device generates user selectable information based on the capability information, the user selectable information including first sub-user selectable information representing one or more capabilities which are supported by the device, and second sub-user selectable capability information representing one or more capabilities which are not supported by the device based on the capability information; and controlling a display screen to display the user selectable information and the content data.
 17. The method of claim 16, comprising: displaying the first sub-user selectable information on a first portion of the display screen, the second sub-user selectable information on a second portion of the display screen, and the content data on a third portion of the display screen.
 18. The method of claim 17, comprising: adjusting at least one of color and brightness of the second portion.
 19. The method of claim 17, wherein the first portion is distinct from the second portion and the third portion, and the second portion is distinct from the third portion.
 20. The method of claim 17, wherein a size of the third portion is greater than a size of the first portion and a size of the second portion.
 21. The method of claim 16, wherein the capability information further includes one or more video formats of video components of the content data, and one or more audio formats of audio components of the content data.
 22. The method of claim 16, comprising: detecting a user input signal to select at least one capability represented by the first sub-user selectable information, in response to detecting the user input signal, displaying the content data in accordance with a selection of the at least one capability.
 23. A device for processing a broadcast signal, the device comprising: a receiver to receive the broadcast signal including primary video data and secondary video data and service guide information, the service guide information including a service fragment including information about a broadcast service and a content fragment, the content fragment including information about a content belonging the broadcast service and information about one or more video components of the secondary video data that is alternative view video data of the primary video data, the primary video data and the secondary video data belonging to the content; a decoder to obtain the service guide information from the broadcast signal to generate user selectable information based on the service guide information, the user selectable information providing information about the secondary video data; a display screen to display the user selectable information and the primary video data; and a controller to detect a user input signal to display the secondary video data, in response to detecting the user input signal, the controller controlling the display screen to display the secondary video data.
 24. The device of claim 23, wherein a primary image corresponding to the primary video data and a secondary image corresponding the secondary video data are partially overlapped.
 25. The device of claim 23, wherein the primary vide data is displayed on a first portion of the display screen and the secondary video data is displayed on a second portion of the display screen.
 26. The device of claim 25, wherein the first portion is distinct from the second portion.
 27. The device of claim 25, wherein the first portion includes the second portion.
 28. The device of claim 23, wherein, the controller is further configured to switch the primary video data on the display screen to the secondary video data in response to detecting the user input signal.
 29. The device of claim 23, the user selectable information further includes pay per view information of the secondary video data.
 30. A method for processing a broadcast signal, the method comprising: receiving the broadcast signal including primary video data and secondary video data and service guide information, the service guide information including a service fragment including information about a broadcast service and a content fragment, the content fragment including information about a content belonging the broadcast service and information about one or more video components of the secondary video data that is alternative view video data of the primary video data, the primary video data and the secondary video data belonging to the content; obtaining the service guide information from the broadcast signal to generate user selectable information based on the service guide information, the user selectable information providing information about the secondary video data; displaying the user selectable information and the primary video data; detecting a user input signal to display the secondary vide data; and in response to detecting the user input signal, controlling a display screen to display the secondary video data.
 31. The method of claim 30, wherein a primary image corresponding to the primary video data and a secondary image corresponding the secondary video data are partially overlapped.
 32. The method of claim 30, wherein the primary video data is displayed on a first portion of a display screen and the secondary video data is displayed on a second portion of the display screen.
 33. The method of claim 32, wherein the first portion is distinct from the second portion.
 34. The method of claim 32, wherein the first portion includes the second portion.
 35. The method of claim 30, comprising: switching the primary video data on the display screen to the secondary video data in response to detecting the user input signal.
 36. The method of claim 30, the user selectable information further includes pay per view information of the secondary video data. 